Triple
T8110883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teron |
E189344
|
entity |
| Predicate | relatedGroup |
P37
|
FINISHED |
| Object | Terang clan |
E715605
|
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: Terang clan | Statement: [Teron, relatedGroup, Terang clan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Terang clan Context triple: [Teron, relatedGroup, Terang clan]
-
A.
Naya clan
The Naya clan is an ancient Jain lineage traditionally associated with the family background of Mahavira, the 24th Tirthankara of Jainism.
-
B.
Timung clan
The Timung clan is a lineage group within the Karbi community of Northeast India, recognized as one of its traditional clans.
-
C.
Javanshir clan
The Javanshir clan was a prominent Azerbaijani noble family that played a significant political and military role in the Karabakh region.
-
D.
Enghee clan
chosen
The Enghee clan is a distinct social or familial group associated with the community or lineage of Teron.
-
E.
Heron clan
The Heron clan is one of the traditional matrilineal clans of the Cayuga people, serving as a key social and kinship group within their Haudenosaunee (Iroquois) cultural system.
- 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_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_69cced062f3881908560b657c096c92e |
completed | April 1, 2026, 10:01 a.m. |
Created at: March 30, 2026, 5:32 p.m.