Triple
T27958776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mi |
E704522
|
entity |
| Predicate | governingFamilyOf |
P196074
|
FINISHED |
| Object | Chu royal house |
—
|
LITERAL 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: Chu royal house | Statement: [Mi, governingFamilyOf, Chu royal house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingFamilyOf Context triple: [Mi, governingFamilyOf, Chu royal house]
-
A.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
B.
intendedFamily
Indicates that one entity is planned or designated to be part of another entity’s family or familial group in the future.
-
C.
describedAsFamilyBy
Indicates that one entity is characterized or referred to as family by another entity.
-
D.
basedOnFamilyOf
Indicates that one entity is derived from, modeled after, or determined by the family, lineage, or familial characteristics of another entity.
-
E.
representsFamily
Indicates that one entity is related to another through a familial relationship (by blood, marriage, or adoption).
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_69fe066b623c819085205fbea901e3cf |
completed | May 8, 2026, 3:51 p.m. |
Created at: April 27, 2026, 7:30 p.m.