Triple
T2509920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morrison Formation |
E52675
|
entity |
| Predicate | timeSpanEndMa |
P35259
|
FINISHED |
| Object | approximately 146 |
—
|
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: approximately 146 | Statement: [Morrison Formation, timeSpanEndMa, approximately 146]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSpanEndMa Context triple: [Morrison Formation, timeSpanEndMa, approximately 146]
-
A.
timePeriodEndApprox
chosen
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
B.
focusPeriodEnd
Indicates the point in time at which a specified focus period or interval concludes.
-
C.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
D.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69ab4958e76481908a235377dd921c9e |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd65d6a988190aaaac8e98540a14f |
completed | March 7, 2026, 7:40 a.m. |
| PD | Predicate disambiguation | batch_69abd0bd996c8190ba8b9d6e4333b8d4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.