Triple
T757160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chechens |
E15581
|
entity |
| Predicate | traditionalConfederationUnit |
P19262
|
FINISHED |
| Object | tukkhum |
—
|
LITERAL 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: tukkhum | Statement: [Chechens, traditionalConfederationUnit, tukkhum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalConfederationUnit Context triple: [Chechens, traditionalConfederationUnit, tukkhum]
-
A.
confederation
Indicates a formal union or alliance between multiple entities that retain their individual autonomy while cooperating under a shared framework or agreement.
-
B.
enteredConfederation
Indicates that an entity became a member of, or formally joined, a confederation.
-
C.
subConfederation
Indicates that one confederation is a subordinate or component part of a larger confederation within a hierarchical organizational structure.
-
D.
associatedConfederationCount
Indicates the number of distinct confederations with which an entity is associated.
-
E.
conventionState
Indicates that an entity is in a particular formal status or phase within a convention or agreed procedural framework.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66ab4608190afcd81e6606c5116 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a50348088190873a1446db657a78 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a62b497081909503c8d30c7ce1db |
completed | March 1, 2026, 8:48 p.m. |
Created at: March 1, 2026, 7:37 p.m.