Triple
T29594445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakasongola District |
E754254
|
entity |
| Predicate | hasMainLivestock |
P45980
|
FINISHED |
| Object | cattle |
—
|
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: cattle | Statement: [Nakasongola District, hasMainLivestock, cattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainLivestock Context triple: [Nakasongola District, hasMainLivestock, cattle]
-
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.
useOfLivestock
Indicates the action or practice of employing livestock for a particular purpose or function.
-
C.
typeOfLivestock
Indicates the specific kind or category of livestock associated with or involved in a given context or entity.
-
D.
livestockUse
Indicates how an entity is used or managed in relation to livestock, such as for raising, feeding, housing, or supporting livestock activities.
-
E.
secondaryLivestock
Indicates that the referenced livestock are of secondary or lesser importance in relation to a primary group of livestock.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
Created at: April 28, 2026, 6:17 p.m.