Triple
T32100768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ji |
E819841
|
entity |
| Predicate | isAncestralNameOf |
P173565
|
FINISHED |
| Object | Kings of 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: Kings of Zhou | Statement: [Ji, isAncestralNameOf, Kings of Zhou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAncestralNameOf Context triple: [Ji, isAncestralNameOf, Kings of Zhou]
-
A.
hasAncestralTo
Indicates that one entity is an ancestor of another, existing in an earlier generation within a lineage or heritage chain.
-
B.
destinedAncestorOf
Indicates that one entity is fated or preordained to become an ancestor of another entity in the future.
-
C.
refersToAncestorNamed
Indicates that an entity refers to an ancestor specifically identified by a given name.
-
D.
hasAncestor
Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
-
E.
isDerivedFromGivenName
Indicates that one entity originates from, or is formed based on, a specified given (first) name.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b695bb248190b53b8056dbcf6b55 |
completed | May 3, 2026, 2:44 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:26 a.m.