Triple
T33674352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Huizhao Xiaode |
E862717
|
entity |
| Predicate | linkedRulerPersonalName |
P166781
|
FINISHED |
| Object | Li Chan |
—
|
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: Li Chan | Statement: [Emperor Huizhao Xiaode, linkedRulerPersonalName, Li Chan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedRulerPersonalName Context triple: [Emperor Huizhao Xiaode, linkedRulerPersonalName, Li Chan]
-
A.
namedPersonAssociation
Indicates a relationship where one entity is associated with or identified by a specific personal name.
-
B.
namedForPersonFullName
Indicates that an entity is named after a specific person, identified by that person’s full name.
-
C.
personalUnionResult
Indicates that a personal union between entities has occurred and specifies the resulting combined political or dynastic arrangement.
-
D.
notableFamilyNameOf
Indicates that a particular family name is notably or prominently associated with a given person or family entity.
-
E.
lastRulerPersonalName
chosen
Indicates the personal name of the most recent or final ruler associated with an entity.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: May 1, 2026, 1:43 a.m.