Triple
T757159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chechens |
E15581
|
entity |
| Predicate | traditionalClanUnit |
P15952
|
FINISHED |
| Object | teip |
—
|
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: teip | Statement: [Chechens, traditionalClanUnit, teip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalClanUnit Context triple: [Chechens, traditionalClanUnit, teip]
-
A.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
B.
clanSystem
chosen
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
C.
associatedClan
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
-
D.
soldierCaste
Indicates that an entity belongs to, or is characterized as part of, a soldier or warrior class within a social or organizational hierarchy.
-
E.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
- 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_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. |
Created at: March 1, 2026, 7:37 p.m.