Triple
T37460662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haunted Creeper |
E930907
|
entity |
| Predicate | boardPresence |
P102598
|
FINISHED |
| Object | High stickiness due to Deathrattle tokens |
—
|
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: High stickiness due to Deathrattle tokens | Statement: [Haunted Creeper, boardPresence, High stickiness due to Deathrattle tokens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardPresence Context triple: [Haunted Creeper, boardPresence, High stickiness due to Deathrattle tokens]
-
A.
boardPresenceRole
Indicates the specific role or capacity in which an entity serves on a board or governing body.
-
B.
bossPresence
Indicates that a boss or supervisor is present in the current context or location.
-
C.
airPresence
Indicates that air is present in or around an entity, typically signifying that the entity contains, is surrounded by, or is exposed to air.
-
D.
managementPresence
Indicates that a management-level individual is present, involved, or overseeing a given context, event, or entity.
-
E.
scenePresence
chosen
Indicates that an entity is present or appears within a particular scene or context.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.