Triple
T17445727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huangjian |
E424776
|
entity |
| Predicate | eraSequenceInNorthernQi |
P127481
|
FINISHED |
| Object | fifth era name of Northern Qi |
—
|
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: fifth era name of Northern Qi | Statement: [Huangjian, eraSequenceInNorthernQi, fifth era name of Northern Qi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraSequenceInNorthernQi Context triple: [Huangjian, eraSequenceInNorthernQi, fifth era name of Northern Qi]
-
A.
eraSequence
Indicates that one era or time period directly follows or precedes another in a chronological sequence.
-
B.
eraNumberInMing
Indicates that a specific era number is assigned within the historical context of the Ming dynasty.
-
C.
Xiaoerjing
Indicates a relationship where something is written, represented, or transcribed using the Xiaoerjing (Arabic-based) script for Sinitic languages.
-
D.
functionInMingDynasty
Indicates that an entity held an official role, position, or function during the Ming Dynasty.
-
E.
nativeDynasty
Indicates that a dynasty is indigenous to, or originally from, the place or polity it rules or is associated with.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ffafec48190b25980318cea353f |
completed | April 19, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:47 a.m.