Triple
T8728350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Funeral Mountains |
E207186
|
entity |
| Predicate | hasRockAge |
P1327
|
FINISHED |
| Object | Precambrian |
—
|
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: Precambrian | Statement: [Funeral Mountains, hasRockAge, Precambrian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRockAge Context triple: [Funeral Mountains, hasRockAge, Precambrian]
-
A.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
B.
hasApproximateDipOfOlderRocks
Indicates that the dip (inclination) of older rock layers is approximately equal to a specified dip value or orientation.
-
C.
hasApproximateDipOfYoungerRocks
Indicates that the younger rock layers have an approximate dip (inclination) of a specified amount or direction relative to horizontal.
-
D.
hasSeafloorAge
Indicates the age of a specified portion of the seafloor relative to a given time or reference point.
-
E.
geologicalAge
chosen
Indicates the time period in Earth's geological history during which an entity (such as a rock, fossil, or formation) originated or was formed.
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d1890e0819088b271db51faa738 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:37 p.m.