Triple
T27887464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Zhao |
E705268
|
entity |
| Predicate | hasAncestralName |
P94994
|
FINISHED |
| Object | Zhao |
—
|
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: Zhao | Statement: [House of Zhao, hasAncestralName, Zhao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralName Context triple: [House of Zhao, hasAncestralName, Zhao]
-
A.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
B.
hasAncestralTitle
Indicates that an entity holds or is associated with a hereditary or historically inherited title passed down through ancestry.
-
C.
hasAncestralTo
Indicates that one entity is an ancestor of another, existing in an earlier generation within a lineage or heritage chain.
-
D.
hasNameInFamily
chosen
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
E.
hasAncestralFamilyNameMeaning
Indicates that an entity’s ancestral family name carries a specific meaning or significance.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 6:34 p.m.