Triple
T479002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inca Empire |
E9123
|
entity |
| Predicate | domesticatedAnimal |
P3598
|
FINISHED |
| Object | llama |
—
|
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: llama | Statement: [Inca Empire, domesticatedAnimal, llama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domesticatedAnimal Context triple: [Inca Empire, domesticatedAnimal, llama]
-
A.
notableDomesticatedSpecies
chosen
Indicates that the subject is a species that is particularly well-known or significant as a domesticated animal.
-
B.
domesticatedFor
Indicates that one entity has been tamed and bred by another for specific human use or benefit.
-
C.
pet
Indicates that one entity keeps another animal for companionship or pleasure, typically providing care and shelter.
-
D.
domestication
Indicates the process by which humans tame and genetically adapt a wild species over time so it can live and reproduce under human control or in close association with people.
-
E.
firstDomesticated
Indicates that one entity was the earliest to domesticate or bring another entity under human control or cultivation.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f056459881909749764cc4a7f9e8 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf1d5848190a7da27e2fddc136f |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.