Triple
T38604860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five (Zombies map) |
E934313
|
entity |
| Predicate | hasMysteryBox |
P191284
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Five (Zombies map), hasMysteryBox, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMysteryBox Context triple: [Five (Zombies map), hasMysteryBox, true]
-
A.
hasMysterySet
Indicates that an entity possesses or includes a collection or configuration whose nature or details are unknown or intentionally concealed.
-
B.
hasMystery
Indicates that one entity possesses, contains, or is associated with something unknown, secret, or unexplained in relation to another entity.
-
C.
hasMysteryType
Indicates that an entity is associated with, categorized under, or characterized by a particular type whose nature or classification is unknown, hidden, or unspecified.
-
D.
hasVIPBoxes
Indicates that an entity provides or contains VIP boxes as part of its facilities or offerings.
-
E.
hasBoxes
Indicates that an entity possesses, contains, or is associated with one or more boxes.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdb0cf6008190b27046b694f84356 |
completed | May 7, 2026, 6:33 p.m. |
Created at: May 3, 2026, 4:32 p.m.