Triple
T28468852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lingzong |
E720373
|
entity |
| Predicate | reignAssociatedWith |
P173378
|
FINISHED |
| Object | Emperor Ling of Han |
—
|
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: Emperor Ling of Han | Statement: [Lingzong, reignAssociatedWith, Emperor Ling of Han]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAssociatedWith Context triple: [Lingzong, reignAssociatedWith, Emperor Ling of Han]
-
A.
reignOfMonarch
Indicates the period during which a specific monarch holds ruling authority over a realm or territory.
-
B.
reignedUnder
Indicates that one entity exercised ruling authority or governance while being subordinate to, or under the higher sovereignty of, another entity.
-
C.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
D.
reignedFrom
Indicates the time period during which an entity held ruling authority or sovereignty over a domain.
-
E.
associatedDynastyRuler
Indicates a relationship where a dynasty is linked to the ruler who governed or is historically connected with it.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 28, 2026, 2:47 a.m.