Triple
T11659007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enderman |
E277076
|
entity |
| Predicate | provokedBy |
P97670
|
FINISHED |
| Object | direct eye contact from player |
—
|
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: direct eye contact from player | Statement: [Enderman, provokedBy, direct eye contact from player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provokedBy Context triple: [Enderman, provokedBy, direct eye contact from player]
-
A.
provokesEmotionType
Indicates that one entity causes or elicits a specific type of emotional response in another entity.
-
B.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
C.
causedReaction
chosen
Indicates that one entity’s action or state brought about a specific reaction or response in another entity.
-
D.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
E.
inducedBy
Indicates that one entity is the cause, source, or triggering factor that brings about the existence, occurrence, or state of another entity.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.