Triple
T33537532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wally West |
E858975
|
entity |
| Predicate | positionInFlashLegacy |
P15235
|
FINISHED |
| Object | third Flash |
—
|
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: third Flash | Statement: [Wally West, positionInFlashLegacy, third Flash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInFlashLegacy Context triple: [Wally West, positionInFlashLegacy, third Flash]
-
A.
positionInFrame
Indicates the spatial location or coordinates of an entity within a specific frame or reference image.
-
B.
positionAt
Indicates that one entity is located at, or occupies, a specific spatial position relative to another entity or reference frame.
-
C.
positionInShow
chosen
Indicates the specific order or placement an entity occupies within a show, series, or sequence of performances or episodes.
-
D.
positionInField
Indicates the specific role, location, or functional placement an entity occupies within a defined field, domain, or area of activity.
-
E.
appearsAtPosition
Indicates that an entity occurs or is located at a specific position within an ordered structure or sequence.
- 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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
Created at: May 1, 2026, 1:39 a.m.