Triple
T13510846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakhtiari tribe |
E321134
|
entity |
| Predicate | seasonalMigration |
P73116
|
FINISHED |
| Object | transhumance |
—
|
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: transhumance | Statement: [Bakhtiari tribe, seasonalMigration, transhumance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalMigration Context triple: [Bakhtiari tribe, seasonalMigration, transhumance]
-
A.
hasSeasonalMigration
chosen
Indicates that an entity regularly moves between different locations according to seasonal or cyclical environmental changes.
-
B.
directionOfMigration
Indicates the geographic direction or path along which a migration movement proceeds from its origin toward its destination.
-
C.
seasonalTourism
Indicates that tourism activity in a place varies significantly by season, with distinct peak and off-peak periods.
-
D.
seasonalPopulation
Indicates a relationship where the number of individuals in a population varies depending on the season or time of year.
-
E.
historicalPopulationMovement
Indicates the movement or migration of a population from one place to another during a specific historical period or event.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf86a6208190be8c18f7a0158f23 |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.