Triple
T8006723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Huai of Chu |
E186380
|
entity |
| Predicate | royalHouse |
P8992
|
FINISHED |
| Object | House of Mi |
E704521
|
NE 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: House of Mi | Statement: [King Huai of Chu, royalHouse, House of Mi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: House of Mi Context triple: [King Huai of Chu, royalHouse, House of Mi]
-
A.
House of Mi
chosen
The House of Mi was the royal family clan that ruled the ancient Chinese state of Chu during the Zhou dynasty.
-
B.
House of Ji
The House of Ji was the hereditary ruling clan of the ancient Chinese State of Lu, traditionally associated with the lineage of the Zhou royal family.
-
C.
House of Kuni
The House of Kuni is a Japanese imperial noble family line to which Empress Kōjun belonged.
-
D.
House of Haro
The House of Haro was a powerful medieval Spanish noble lineage that held the lordship of Biscay and played a significant role in the politics of the Kingdom of Castile.
-
E.
House of Jochi
The House of Jochi was the ruling dynasty descended from Jochi, eldest son of Genghis Khan, which governed major Mongol successor states such as the Golden Horde.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf8a6048190970685a83fd2f59d |
completed | March 31, 2026, 3:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc5697ac9081909fe7ca06d0c3ef38 |
completed | March 31, 2026, 11:19 p.m. |
Created at: March 30, 2026, 5:18 p.m.