Triple
T38464444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Komodo Joe |
E912527
|
entity |
| Predicate | gameplayRoleInCTR |
P100032
|
FINISHED |
| Object | unlockable character |
—
|
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: unlockable character | Statement: [Komodo Joe, gameplayRoleInCTR, unlockable character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameplayRoleInCTR Context triple: [Komodo Joe, gameplayRoleInCTR, unlockable character]
-
A.
roleInGameplay
chosen
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
B.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
C.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
D.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
E.
playRoleIn
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.