Triple
T26996128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caprinae |
E679983
|
entity |
| Predicate | notableDomesticatedMember |
P34928
|
FINISHED |
| Object | domestic goat |
—
|
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: domestic goat | Statement: [Caprinae, notableDomesticatedMember, domestic goat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDomesticatedMember Context triple: [Caprinae, notableDomesticatedMember, domestic goat]
-
A.
notableDomesticatedSpecies
Indicates that the subject is a species that is particularly well-known or significant as a domesticated animal.
-
B.
domesticatedMembers
chosen
Indicates that certain members of a group or species have been tamed and adapted to live in close association with humans, typically under human care or control.
-
C.
firstDomesticatedSpecies
Indicates that the subject is the earliest species to have been domesticated by the object (e.g., a human group or civilization).
-
D.
wasDomesticatedIn
Indicates that an entity became domesticated during or within a specified time period or historical era.
-
E.
isDomesticated
Indicates that an entity has been tamed and bred by humans to live and function under human care or control.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: April 27, 2026, 6:54 a.m.