Triple
T28395893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daji |
E719286
|
entity |
| Predicate | timeFrameInLegend |
P25762
|
FINISHED |
| Object | 11th century BCE (traditional dating) |
—
|
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: 11th century BCE (traditional dating) | Statement: [Daji, timeFrameInLegend, 11th century BCE (traditional dating)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeFrameInLegend Context triple: [Daji, timeFrameInLegend, 11th century BCE (traditional dating)]
-
A.
timePeriodOfLegend
chosen
Indicates the time period during which a particular legend is traditionally set or believed to have occurred.
-
B.
timeAxisOftenLabeled
Indicates that the time axis in a representation (such as a chart or graph) is frequently given an explicit label.
-
C.
timeFrameSpecified
Indicates that a specific temporal period or duration has been explicitly defined or constrained for the related event, action, or relationship.
-
D.
timeFrameTraditionallyLinked
Indicates that one time frame is customarily or historically associated with another, reflecting a traditional linkage between them.
-
E.
timeScaleCategory
Indicates the classification of an event or process based on the temporal scale or duration over which it occurs.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 1:16 a.m.