Triple
T27971417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taiping Xingguo |
E706365
|
entity |
| Predicate | eraNumberInDynasty |
P163583
|
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: [Taiping Xingguo, eraNumberInDynasty, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraNumberInDynasty Context triple: [Taiping Xingguo, eraNumberInDynasty, 2]
-
A.
dynasticNumber
Indicates the ordinal position or identifying number assigned to a dynasty within a historical or genealogical sequence.
-
B.
eraNumberUnderEmperorYang
Indicates that the specified era name or era number was used during the reign of Emperor Yang.
-
C.
positionInDynasty
Indicates the specific role or rank an individual holds within a particular dynasty’s internal hierarchy.
-
D.
reignInDynasty
Indicates that a person’s reign or rule occurs within the context of a specific dynasty.
-
E.
ordinalNumberAsEmperor
Indicates the numerical order in which a person held the title or role of emperor.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b35079c819084779003fe29410d |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 7:38 p.m.