Triple
T28601343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Di Yi |
E723919
|
entity |
| Predicate | eraBefore |
P164898
|
FINISHED |
| Object | Western Zhou dynasty |
—
|
NE NERFINISHED |
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: Western Zhou dynasty | Statement: [King Di Yi, eraBefore, Western Zhou dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraBefore Context triple: [King Di Yi, eraBefore, Western Zhou dynasty]
-
A.
eraStart
Indicates the point in time at which a particular era or period begins.
-
B.
eraEnd
Indicates the point in time or event at which a particular era, period, or phase comes to a close.
-
C.
era
Indicates that something existed, occurred, or was valid during a specified historical or temporal period.
-
D.
eraReference
Indicates a temporal relationship where something is associated with, situated in, or characterized by a particular historical era or time period.
-
E.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f652a3a8208190a4fdd66f34138bd2 |
completed | May 2, 2026, 7:38 p.m. |
Created at: April 28, 2026, 4:24 a.m.