Triple
T28289918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King An of Han |
E713394
|
entity |
| Predicate | finalRulerOf |
P48946
|
FINISHED |
| Object | State 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: State of Han | Statement: [King An of Han, finalRulerOf, State of Han]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalRulerOf Context triple: [King An of Han, finalRulerOf, State of Han]
-
A.
finalRuler
chosen
Indicates that an entity is the last or ultimate ruler of another entity, with no subsequent rulers following.
-
B.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
C.
concludedUnderRuler
Indicates that an event, agreement, or process was completed or finalized during the reign or authority of a specific ruler.
-
D.
ruledOnBy
Indicates that a decision, case, or matter has been formally decided or adjudicated by a specific authority or decision-maker.
-
E.
alsoRuled
Indicates that two or more entities shared ruling authority over the same domain or subjects, either concurrently or at different times.
- F. None of above.
Provenance (3 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 27, 2026, 11:28 p.m.