Triple
T38604858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five (Zombies map) |
E934313
|
entity |
| Predicate | hasBossRound |
P15100
|
FINISHED |
| Object | Pentagon Thief rounds |
—
|
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: Pentagon Thief rounds | Statement: [Five (Zombies map), hasBossRound, Pentagon Thief rounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBossRound Context triple: [Five (Zombies map), hasBossRound, Pentagon Thief rounds]
-
A.
hasBoss
Indicates that one entity serves as the direct superior or manager of another entity in a hierarchical relationship.
-
B.
hasRound
chosen
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
-
C.
hasBossForm
Indicates that an entity has a special, typically more powerful "boss" version or transformation form.
-
D.
hasActingBoss
Indicates that an entity is under the authority or supervision of a temporary or interim boss.
-
E.
isAfterBoss
Indicates that one entity occurs or is positioned later in sequence or time than the boss 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 3, 2026, 4:32 p.m.