Triple
T10835508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New World vultures |
E255744
|
entity |
| Predicate | benefitsToHumans |
P43904
|
FINISHED |
| Object | removal of animal carcasses |
—
|
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: removal of animal carcasses | Statement: [New World vultures, benefitsToHumans, removal of animal carcasses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitsToHumans Context triple: [New World vultures, benefitsToHumans, removal of animal carcasses]
-
A.
benefitForEarth
Indicates that an action, object, or condition provides a positive impact or advantage specifically for the Earth or its environment.
-
B.
impactOnHumans
chosen
Indicates a relationship where something produces an effect, influence, or consequence on humans.
-
C.
humanImpact
Indicates the effect or influence that human activities have on another entity, system, or environment.
-
D.
hasEconomicImportanceFor
Indicates that one entity holds economic value, benefit, or significance for another entity.
-
E.
conflictsWithHumans
Indicates a relationship where an entity is in opposition, dispute, or hostile interaction with humans, leading to incompatibility or clashes between their interests or actions.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d746fdefd4819099772efbd4f302cb |
completed | April 9, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.