Triple
T11444741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nilgai |
E271233
|
entity |
| Predicate | conflictWithHumans |
P33584
|
FINISHED |
| Object | crop raiding |
—
|
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: crop raiding | Statement: [nilgai, conflictWithHumans, crop raiding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictWithHumans Context triple: [nilgai, conflictWithHumans, crop raiding]
-
A.
conflictsWithHumans
chosen
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.
-
B.
threatToHumans
Indicates that the subject poses or represents a potential danger, harm, or risk to humans.
-
C.
conflictOrCooperationWith
Indicates the presence, nature, or degree of either conflict or cooperation between two entities.
-
D.
impactOnHumans
Indicates a relationship where something produces an effect, influence, or consequence on humans.
-
E.
humanImpact
Indicates the effect or influence that human activities have on another entity, system, or environment.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8088a66f48190b2b4a56cd62097cf |
completed | April 9, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.