Triple
T37087875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalbeliya tribe |
E918337
|
entity |
| Predicate | currentLivelihood |
P29524
|
FINISHED |
| Object | stage performances |
—
|
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: stage performances | Statement: [Kalbeliya tribe, currentLivelihood, stage performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentLivelihood Context triple: [Kalbeliya tribe, currentLivelihood, stage performances]
-
A.
livelihood
chosen
Indicates that one entity serves as the primary means of support, income, or subsistence for another entity.
-
B.
livelihoodArea
Indicates the area or domain in which an entity earns its living or sustains its means of support.
-
C.
livelihoodChange
Indicates a change in a person’s or group’s means of making a living, such as improvements, declines, or shifts in income-generating activities.
-
D.
livelihoodChallenges
Indicates difficulties or obstacles that negatively affect an entity’s ability to secure or maintain its means of living or income.
-
E.
currentLivingStandard
Indicates the present quality or level of material well-being and daily living conditions experienced by an entity.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffa9677be08190852c8ef6c2545fed |
completed | May 9, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69ffa6570e2c8190a9d7b37f12b91d9a |
completed | May 9, 2026, 9:25 p.m. |
Created at: May 3, 2026, 4:14 p.m.