Triple
T30192163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiande |
E767519
|
entity |
| Predicate | usedByRulingHouse |
P55345
|
FINISHED |
| Object | Guo family of Later Zhou |
—
|
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: Guo family of Later Zhou | Statement: [Xiande, usedByRulingHouse, Guo family of Later Zhou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByRulingHouse Context triple: [Xiande, usedByRulingHouse, Guo family of Later Zhou]
-
A.
usedByNobleFamily
chosen
Indicates that something is employed, possessed, or otherwise utilized by a noble family.
-
B.
rulingHouse
Indicates that one entity serves as the dynastic or noble family that holds ruling authority over another entity, such as a state, territory, or polity.
-
C.
usedByRulersOf
Indicates that something is employed, utilized, or otherwise put to use by rulers or governing authorities.
-
D.
hasRoyalHousehold
Indicates that an entity possesses or is associated with a specific royal household as its official domestic or courtly establishment.
-
E.
usedInMonarchy
Indicates that something is employed, practiced, or functions within the context of a monarchical system of government.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 29, 2026, 7:29 p.m.