Triple
T35394634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokey |
E1023037
|
entity |
| Predicate | targetPlayerCharacter |
P41757
|
FINISHED |
| Object | Playable characters in Mario games |
—
|
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: Playable characters in Mario games | Statement: [Pokey, targetPlayerCharacter, Playable characters in Mario games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPlayerCharacter Context triple: [Pokey, targetPlayerCharacter, Playable characters in Mario games]
-
A.
targetsCharacter
Indicates that one entity is the intended focus or target of another entity’s action, effect, or behavior.
-
B.
mainCharacterActor
Indicates that the specified actor portrays the main character in a given work (such as a film, show, or play).
-
C.
currentCharacter
chosen
Indicates that an entity is the character presently in focus or being actively considered in a given context or sequence.
-
D.
mainCharacterField
Indicates that one entity is designated as the primary or central character associated with another entity, such as a work or narrative.
-
E.
controllingPlayer
Indicates which player currently has control or authority over a given game element, object, or situation.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:03 p.m.