Triple
T26618306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infinity Formula |
E668125
|
entity |
| Predicate | usedInStoryline |
P115762
|
FINISHED |
| Object | Nick Fury vs. S.H.I.E.L.D. |
—
|
NE NERFINISHED |
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: Nick Fury vs. S.H.I.E.L.D. | Statement: [Infinity Formula, usedInStoryline, Nick Fury vs. S.H.I.E.L.D.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInStoryline Context triple: [Infinity Formula, usedInStoryline, Nick Fury vs. S.H.I.E.L.D.]
-
A.
usedInSeries
Indicates that something (such as an element, component, or concept) is employed or appears within a particular series.
-
B.
useInNarrative
chosen
Indicates that something is employed as an element or device within a narrative or story.
-
C.
controlledByInStory
Indicates that, within the context of a specific story or narrative, one entity exercises control or authority over another.
-
D.
activeDuringStoryline
Indicates that an entity is active or relevant throughout the duration of a specified storyline or narrative arc.
-
E.
usedInStage
Indicates that something is utilized or applied during a particular stage or phase of a process or workflow.
- 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 2:19 a.m.