Triple
T37661376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enderman |
E937724
|
entity |
| Predicate | becomesHostileWhen |
P188590
|
FINISHED |
| Object | player looks at its head |
—
|
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: player looks at its head | Statement: [Enderman, becomesHostileWhen, player looks at its head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becomesHostileWhen Context triple: [Enderman, becomesHostileWhen, player looks at its head]
-
A.
hostilityRange
Indicates the distance within which an entity will treat another as a hostile target and may initiate or respond with aggressive actions.
-
B.
belligerentAgainst
Indicates a hostile or aggressive stance, conflict, or antagonistic behavior directed by one entity against another.
-
C.
temporarilyEnemyOf
Indicates a relationship where two entities are in a state of enmity or opposition for a limited, non-permanent period of time.
-
D.
hostileRange
Indicates that one entity is within the distance at which another entity is considered hostile or can engage in hostile actions.
-
E.
initiallyEnemyOf
Indicates that one entity starts out in a state of enmity or opposition toward another at the beginning of a specified time or situation.
- F. None of above. chosen
Provenance (4 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa19e4a88190b04f26c0d4e708fd |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbaa108ee48190b84d13df3ef3e365 |
completed | May 6, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:18 p.m.