Triple
T17041734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appalachian Basin |
E413460
|
entity |
| Predicate | hasRockThickness |
P117691
|
FINISHED |
| Object | several kilometers |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: several kilometers | Statement: [Appalachian Basin, hasRockThickness, several kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRockThickness Context triple: [Appalachian Basin, hasRockThickness, several kilometers]
-
A.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
B.
hasStratigraphicThickness
chosen
Indicates the measured vertical thickness or depth extent of a stratigraphic unit or layer.
-
C.
hasCrustalThickness
Indicates the relationship in which an object or region possesses a specified thickness of its crust.
-
D.
hasRockTalusAtBase
Indicates that a rock talus deposit is present at the base of something, typically accumulating at the bottom of a slope, cliff, or similar feature.
-
E.
hasMaximumThickness
Indicates that an entity possesses a specified upper limit on its thickness.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8f771608190b596138ddec118c6 |
completed | April 18, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.