Triple
T36960609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sentinel Hammer |
E914296
|
entity |
| Predicate | inGameCategory |
P142353
|
FINISHED |
| Object | equipment |
—
|
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: equipment | Statement: [Sentinel Hammer, inGameCategory, equipment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inGameCategory Context triple: [Sentinel Hammer, inGameCategory, equipment]
-
A.
inGameType
Indicates that an entity participates in or belongs to a specific type or category within a game (e.g., game mode, classification, or role).
-
B.
hasInGameCategory
chosen
Indicates that an in-game item, action, or entity belongs to a specific predefined category within the game’s classification system.
-
C.
inGameZone
Indicates that an entity is located within a defined game zone or area of the game world.
-
D.
inGameName
Indicates that one entity is the name used by another entity within a specific game context.
-
E.
playsCategory
Indicates that an entity engages in or performs activities belonging to a specified category.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.