Triple
T8110882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teron |
E189344
|
entity |
| Predicate | relatedGroup |
P37
|
FINISHED |
| Object |
Enghee clan
The Enghee clan is a distinct social or familial group associated with the community or lineage of Teron.
|
E715605
|
NE FINISHED |
How this triple was built (4 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: Enghee clan | Statement: [Teron, relatedGroup, Enghee clan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Enghee clan Context triple: [Teron, relatedGroup, Enghee clan]
-
A.
Javanshir clan
The Javanshir clan was a prominent Azerbaijani noble family that played a significant political and military role in the Karabakh region.
-
B.
Nagan Kim clan
The Nagan Kim clan is a Korean family lineage originating from the Nagan region, belonging to the broader Kim surname lineage.
-
C.
Nanbu clan
The Nanbu clan was a powerful samurai family that ruled much of northern Honshu, particularly the Morioka domain in Mutsu Province, throughout Japan’s feudal era.
-
D.
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.
-
E.
Timung clan
The Timung clan is a lineage group within the Karbi community of Northeast India, recognized as one of its traditional clans.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Enghee clan Triple: [Teron, relatedGroup, Enghee clan]
Generated description
The Enghee clan is a distinct social or familial group associated with the community or lineage of Teron.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Enghee clan Target entity description: The Enghee clan is a distinct social or familial group associated with the community or lineage of Teron.
-
A.
Javanshir clan
The Javanshir clan was a prominent Azerbaijani noble family that played a significant political and military role in the Karabakh region.
-
B.
Nagan Kim clan
The Nagan Kim clan is a Korean family lineage originating from the Nagan region, belonging to the broader Kim surname lineage.
-
C.
Nanbu clan
The Nanbu clan was a powerful samurai family that ruled much of northern Honshu, particularly the Morioka domain in Mutsu Province, throughout Japan’s feudal era.
-
D.
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.
-
E.
Timung clan
The Timung clan is a lineage group within the Karbi community of Northeast India, recognized as one of its traditional clans.
- F. None of above. chosen
Provenance (5 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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42fcfb9c81908496f9a7e30d0d8a |
completed | March 31, 2026, 3:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ccbe994fc881908a43cfdf9f28753c |
completed | April 1, 2026, 6:43 a.m. |
| NEDg | Description generation | batch_69ccc37113108190901b02fae92764cf |
completed | April 1, 2026, 7:04 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ccd7eca618819081e0c5452c8b1960 |
completed | April 1, 2026, 8:31 a.m. |
Created at: March 30, 2026, 5:32 p.m.