Triple
T10569119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teda people |
E249431
|
entity |
| Predicate | herdingType |
P47296
|
FINISHED |
| Object | camel herding |
—
|
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: camel herding | Statement: [Teda people, herdingType, camel herding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: herdingType Context triple: [Teda people, herdingType, camel herding]
-
A.
herdedBy
Indicates that one entity is gathered, driven, or controlled as a group by another entity, typically in the manner of a herder managing a herd.
-
B.
typeOfLivestock
chosen
Indicates the specific kind or category of livestock associated with or involved in a given context or entity.
-
C.
breedsIn
Indicates that an organism reproduces or carries out its breeding activities within a specified environment, habitat, or location.
-
D.
isHeritageBreed
Indicates that an animal breed belongs to a traditional, historically established lineage recognized for its cultural, genetic, or agricultural heritage.
-
E.
ruminantType
Indicates that one entity is classified as a type or category within the group of ruminant animals in relation to another 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52730fd4481908b3f4eb80ca209f2 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:37 p.m.