Triple
T19505285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadow Monster |
E488004
|
entity |
| Predicate | hasGameRole |
P100032
|
FINISHED |
| Object | monster |
—
|
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: monster | Statement: [Shadow Monster, hasGameRole, monster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGameRole Context triple: [Shadow Monster, hasGameRole, monster]
-
A.
roleInGameplay
chosen
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
B.
hasStageRole
Indicates that an entity performs or holds a specific role or character in a staged performance or theatrical production.
-
C.
hasFranchiseRole
Indicates that an entity holds a specific role or position within a franchise relationship.
-
D.
hasLegalRole
Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
-
E.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e635113fdc819098ea0f738d01925c |
completed | April 20, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.