Triple
T19571292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumbawa people |
E489720
|
entity |
| Predicate | livestockSpecialty |
P45980
|
FINISHED |
| Object | Sumbawa horses |
—
|
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: Sumbawa horses | Statement: [Sumbawa people, livestockSpecialty, Sumbawa horses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livestockSpecialty Context triple: [Sumbawa people, livestockSpecialty, Sumbawa horses]
-
A.
primaryLivestock
chosen
Indicates that the specified livestock type is the main or most important kind of animal raised or kept by an entity.
-
B.
livestockUse
Indicates how an entity is used or managed in relation to livestock, such as for raising, feeding, housing, or supporting livestock activities.
-
C.
typeOfLivestock
Indicates the specific kind or category of livestock associated with or involved in a given context or entity.
-
D.
pastoralActivities
Indicates activities related to providing spiritual care, guidance, or religious leadership within a community.
-
E.
pastoralPurpose
Indicates that something is intended or designated for pastoral use, care, or ministry within a religious or spiritual context.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402103208190b80acdfa82b7a9c4 |
completed | April 20, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.