Triple
T9523002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statherian Period |
E229689
|
entity |
| Predicate | chronologyType |
P88531
|
FINISHED |
| Object | absolute age–defined period |
—
|
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: absolute age–defined period | Statement: [Statherian Period, chronologyType, absolute age–defined period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyType Context triple: [Statherian Period, chronologyType, absolute age–defined period]
-
A.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
B.
chronologyNote
Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
-
C.
chronologyCertainty
Indicates the degree of confidence or uncertainty about the ordering or dating of events or temporal relationships.
-
D.
chronologyEstablishedBy
Indicates that the temporal order or dating of events, objects, or periods is determined or defined by a specified source, method, or authority.
-
E.
chronologyStart
Indicates the point in time at which a sequence, event, or temporal record begins.
- F. None of above. chosen
Provenance (4 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_69ca847870a881909d8d751a7d29da39 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9898e0b48190a3e3f0f1616d5055 |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca89f1d748190bf3636bea28d8a37 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:59 p.m.