Triple
T1633466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elephant Lands |
E35308
|
entity |
| Predicate | animalWelfareGoal |
P10570
|
FINISHED |
| Object | encourage natural elephant behaviors |
—
|
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: encourage natural elephant behaviors | Statement: [Elephant Lands, animalWelfareGoal, encourage natural elephant behaviors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: animalWelfareGoal Context triple: [Elephant Lands, animalWelfareGoal, encourage natural elephant behaviors]
-
A.
sacrificeAnimalType
Indicates that an entity performs or is involved in the act of sacrificing an animal of a specified type.
-
B.
welfareConcern
chosen
Indicates that one entity has a concern, issue, or responsibility related to the welfare or well-being of another entity.
-
C.
aimsToProtect
Indicates an intention or purpose to safeguard or defend one entity, value, or condition from harm, risk, or undesirable outcomes.
-
D.
usedAnimal
Indicates that one entity employed or exploited an animal for a particular purpose or activity.
-
E.
companionAnimals
Indicates a relationship where one entity keeps or cares for another entity as a pet or companion animal.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907cac610819083cafd4396b6d66c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.