Triple
T8618316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhou state |
E204097
|
entity |
| Predicate | dynasty |
P1547
|
FINISHED |
| Object | Ji clan |
E728441
|
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: Ji clan | Statement: [Zhou state, dynasty, Ji clan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ji clan Context triple: [Zhou state, dynasty, Ji clan]
-
A.
Ji clan
The Ji clan was one of the three powerful aristocratic lineages that dominated the politics of the ancient Chinese State of Lu during the Spring and Autumn period.
-
B.
Ji clan
chosen
The Ji clan was the aristocratic lineage that held hereditary power as the ruling family of the ancient Chinese State of Yan during the Zhou dynasty period.
-
C.
Enghee clan
The Enghee clan is a distinct social or familial group associated with the community or lineage of Teron.
-
D.
Han clan
The Han clan was one of the powerful aristocratic lineages in ancient China that emerged as a major feudal state following the breakup of the Jin kingdom during the Warring States period.
-
E.
Ronghang clan
The Ronghang clan is a lineage group within the Karbi community of Northeast India, recognized as one of its traditional clans.
- 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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc4712e74c81908b607a0ab2f9a361 |
completed | March 31, 2026, 10:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cecc92beb48190ad406f48e58d9d0c |
completed | April 2, 2026, 8:07 p.m. |
Created at: March 30, 2026, 6:26 p.m.