Triple
T36501705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barskhan tribe |
E899346
|
entity |
| Predicate | nomadicOrSedentary |
P1830
|
FINISHED |
| Object | nomadic |
—
|
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: nomadic | Statement: [Barskhan tribe, nomadicOrSedentary, nomadic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nomadicOrSedentary Context triple: [Barskhan tribe, nomadicOrSedentary, nomadic]
-
A.
historicallyNomadic
Indicates that an entity has traditionally led a mobile, wandering lifestyle without permanent settlement over a significant historical period.
-
B.
historicalPeriodOfSedentarization
Indicates the historical time period during which an entity transitioned from a nomadic or mobile lifestyle to a settled, sedentary way of living.
-
C.
humanSettlementType
Indicates the classification of a human settlement based on its form or function, such as village, town, or city.
-
D.
originOfSettlement
Indicates the place, source, or starting point from which a settlement was established or originated.
-
E.
hadPrimarySettlementPattern
chosen
Indicates that an entity exhibited or was characterized by a particular dominant form or arrangement of human settlement.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.