Triple
T37467354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resistance 2 |
E931063
|
entity |
| Predicate | storyFollows |
P28389
|
FINISHED |
| Object | Nathan Hale's infection by the Chimera virus |
—
|
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: Nathan Hale's infection by the Chimera virus | Statement: [Resistance 2, storyFollows, Nathan Hale's infection by the Chimera virus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyFollows Context triple: [Resistance 2, storyFollows, Nathan Hale's infection by the Chimera virus]
-
A.
followsStoryOf
chosen
Indicates that one narrative, account, or storyline continues from, is based on, or is derived from the events or structure of another.
-
B.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
C.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
D.
followsPlot
Indicates that one narrative element adheres to, continues, or is consistent with the storyline established by another.
-
E.
followsSeries
Indicates that one entity comes after another as the next installment or continuation within an ordered series.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.