Triple
T11658915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creeper |
E277074
|
entity |
| Predicate | despawnCondition |
P64498
|
FINISHED |
| Object | when player is far away |
—
|
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: when player is far away | Statement: [Creeper, despawnCondition, when player is far away]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: despawnCondition Context triple: [Creeper, despawnCondition, when player is far away]
-
A.
removalCondition
chosen
Indicates the condition or circumstances under which an entity is removed, deleted, or no longer considered applicable.
-
B.
diesAfterSpawning
Indicates that an entity dies shortly after producing offspring or completing its spawning process.
-
C.
detonationCondition
Indicates the specific circumstances or triggers under which a detonation occurs or is initiated.
-
D.
terminationCondition
Indicates the condition or set of conditions under which an ongoing process, activity, or relationship is brought to an end.
-
E.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
- 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_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.