Triple
T23582044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bor Dinka |
E582230
|
entity |
| Predicate | livestockImportance |
P152800
|
FINISHED |
| Object | central to social status |
—
|
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: central to social status | Statement: [Bor Dinka, livestockImportance, central to social status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livestockImportance Context triple: [Bor Dinka, livestockImportance, central to social status]
-
A.
livestockUse
Indicates how an entity is used or managed in relation to livestock, such as for raising, feeding, housing, or supporting livestock activities.
-
B.
primaryLivestock
Indicates that the specified livestock type is the main or most important kind of animal raised or kept by an entity.
-
C.
typeOfLivestock
Indicates the specific kind or category of livestock associated with or involved in a given context or entity.
-
D.
hasEconomicImportanceFor
Indicates that one entity holds economic value, benefit, or significance for another entity.
-
E.
agriculturalImplication
Indicates a relationship where one factor, event, or condition has consequences, effects, or relevance specifically within an agricultural context.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b02cf4e0819094ff4e406cda270d |
completed | April 29, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:40 p.m.