Triple
T18698679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daye |
E457187
|
entity |
| Predicate | eraNumberUnderEmperorYang |
P132345
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Daye, eraNumberUnderEmperorYang, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraNumberUnderEmperorYang Context triple: [Daye, eraNumberUnderEmperorYang, 2]
-
A.
ordinalNumberAsEmperor
Indicates the numerical order in which a person held the title or role of emperor.
-
B.
eraNumberInMing
Indicates that a specific era number is assigned within the historical context of the Ming dynasty.
-
C.
reigningEmperorPersonalName
Indicates the personal name of the individual who is currently serving as the reigning emperor.
-
D.
hasEmperor
Indicates that an entity is ruled or governed by an emperor.
-
E.
laterSupportedEmperor
Indicates that an entity provided support to an emperor at a later time or stage, rather than during the emperor’s initial rise or earlier period.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e984988190ae902d41edd8faff |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:49 a.m.