Triple
T13870790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hettangian stage |
E333442
|
entity |
| Predicate | timeEndUncertaintyMa |
P35787
|
FINISHED |
| Object | 0.3 |
—
|
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: 0.3 | Statement: [Hettangian stage, timeEndUncertaintyMa, 0.3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeEndUncertaintyMa Context triple: [Hettangian stage, timeEndUncertaintyMa, 0.3]
-
A.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
B.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
-
C.
endTimeApproximate
chosen
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
D.
statusEndsWhen
Indicates that a particular status or condition ceases to hold when a specified event, time, or state occurs.
-
E.
endTimeAsConsort
Indicates the point in time when an individual's role or status as a consort to another person comes to an end.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a101488190bd790b28033d38b9 |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69de05972f3881909977b4c843984f88 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:14 p.m.