Triple
T8631937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Javan rusa |
E204422
|
entity |
| Predicate | domesticatedUse |
P10558
|
FINISHED |
| Object | farmed for meat |
—
|
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: farmed for meat | Statement: [Javan rusa, domesticatedUse, farmed for meat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domesticatedUse Context triple: [Javan rusa, domesticatedUse, farmed for meat]
-
A.
domesticatedFor
chosen
Indicates that one entity has been tamed and bred by another for specific human use or benefit.
-
B.
isDomesticated
Indicates that an entity has been tamed and bred by humans to live and function under human care or control.
-
C.
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.
-
D.
domesticatedFrom
Indicates that one organism or population has been domesticated from, or originates as a domesticated form of, another organism or population.
-
E.
domesticatedBy
Indicates that one entity has been tamed and bred by another, typically a human or group, for companionship, work, or other purposes.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc47944d1c819081f448f14d04bf9d |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.