Triple
T28804803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shulaveri–Shomu culture |
E727342
|
entity |
| Predicate | practicedAnimalHusbandry |
P47296
|
FINISHED |
| Object | cattle 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: cattle herding | Statement: [Shulaveri–Shomu culture, practicedAnimalHusbandry, cattle herding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: practicedAnimalHusbandry Context triple: [Shulaveri–Shomu culture, practicedAnimalHusbandry, cattle herding]
-
A.
animalWelfarePractice
Indicates practices, actions, or policies that affect the well-being, treatment, and living conditions of animals.
-
B.
useOfLivestock
Indicates the action or practice of employing livestock for a particular purpose or function.
-
C.
primaryLivestock
Indicates that the specified livestock type is the main or most important kind of animal raised or kept by an entity.
-
D.
domesticationCenter
Indicates the place or region where a species was first brought under human control and selectively bred, marking the origin of its domestication.
-
E.
typeOfLivestock
chosen
Indicates the specific kind or category of livestock associated with or involved in a given context or 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:28 a.m.