Triple
T10817965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plainview, Texas |
E255281
|
entity |
| Predicate | livestockIndustry |
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: [Plainview, Texas, livestockIndustry, cattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livestockIndustry Context triple: [Plainview, Texas, livestockIndustry, cattle]
-
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
chosen
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.
pastoralActivities
Indicates activities related to providing spiritual care, guidance, or religious leadership within a community.
-
E.
agriculturalFocus
Indicates that an entity is primarily concerned with, oriented toward, or specializing in agriculture or farming-related activities.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7344866f88190be4addb7c8020fce |
completed | April 9, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:18 p.m.