Triple
T1821468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doric order |
E40547
|
entity |
| Predicate | earliestUseCenturyBCE |
P11259
|
FINISHED |
| Object | 7th century BCE |
—
|
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: 7th century BCE | Statement: [Doric order, earliestUseCenturyBCE, 7th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestUseCenturyBCE Context triple: [Doric order, earliestUseCenturyBCE, 7th century BCE]
-
A.
approximateBirthCenturyBCE
Indicates that an entity’s birth is estimated to have occurred within a specified century before the Common Era (BCE), rather than on an exact year or date.
-
B.
attestedUntilCentury
Indicates the latest century up to which the existence or use of something is historically documented or evidenced.
-
C.
approximateStartCenturyBC
chosen
Indicates that an entity’s starting time or occurrence is approximately located within a specified century before the Common Era (BC).
-
D.
locationOfEarlyUse
Indicates the place where something was first or among the earliest instances to be used or applied.
-
E.
attestedFromCentury
Indicates the century from which there is evidence or documentation that something is known to exist or be in use.
- 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_69a8864526c081908a3a4d74f689e2c5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba67721788190951beae25e885457 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61d884548190a19cf3a6b5ae9d48 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.