Triple
T28047124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xuande |
E708713
|
entity |
| Predicate | bearerClan |
P1915
|
FINISHED |
| Object | Liu clan of Zhuo |
—
|
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: Liu clan of Zhuo | Statement: [Xuande, bearerClan, Liu clan of Zhuo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerClan Context triple: [Xuande, bearerClan, Liu clan of Zhuo]
-
A.
clanType
Indicates the specific category or classification of a clan within a broader clan system or hierarchy.
-
B.
associatedClan
chosen
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
-
C.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
D.
associatedClanChief
Indicates a relationship where an entity is linked or connected to a particular clan chief, typically as the chief responsible for or representing that entity.
-
E.
clanCrestAssociatedWith
Indicates that a particular clan crest is symbolically or traditionally linked to a specific clan or family.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 8:30 p.m.