Triple
T17912676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parallax |
E447850
|
entity |
| Predicate | roleInStoryline |
P42552
|
FINISHED |
| Object | cause of Hal Jordan’s fall |
—
|
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: cause of Hal Jordan’s fall | Statement: [Parallax, roleInStoryline, cause of Hal Jordan’s fall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInStoryline Context triple: [Parallax, roleInStoryline, cause of Hal Jordan’s fall]
-
A.
roleInStories
chosen
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
B.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
C.
roleInDialogue
Indicates that an entity participates in a dialogue with a specific conversational role (e.g., speaker, listener, moderator) relative to other participants.
-
D.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
-
E.
metaNarrativeRole
Indicates the narrative function or role that one element (such as a character, voice, or device) plays in commenting on, framing, or reflecting the story itself at a meta-level.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a30288ac8190bc633e69447709bf |
completed | April 19, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.