Triple
T33891411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matthew Malone |
E868776
|
entity |
| Predicate | hasPrimaryCharacterArcIn |
P196218
|
FINISHED |
| Object | Game On |
E246851
|
NE 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: Game On | Statement: [Matthew Malone, hasPrimaryCharacterArcIn, Game On]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryCharacterArcIn Context triple: [Matthew Malone, hasPrimaryCharacterArcIn, Game On]
-
A.
hasNarrativeArcIn
chosen
Indicates that an entity’s storyline or narrative progression occurs within or is contained by a specified work, context, or medium.
-
B.
hasNarrativeArcOf
Indicates that one entity embodies, represents, or corresponds to the narrative arc (story progression or plot structure) of another entity.
-
C.
hasPrimaryCharacter
Indicates that an entity features another entity as its main or central character.
-
D.
characterArcElement
Indicates that one element is a component or stage within a character’s overall developmental arc or transformation.
-
E.
characterArc
Indicates the developmental journey or transformation a character undergoes over the course of a narrative.
- F. None of above.
Provenance (4 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a020243e2b4819086dbfdcf4372405e |
completed | May 11, 2026, 4:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36c1af01fc81908ff6d3a5b188240f |
completed | June 20, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_6a0200f585bc8190b774c54cec409b00 |
completed | May 11, 2026, 4:16 p.m. |
Created at: May 1, 2026, 1:48 a.m.