Triple
T28306921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rambaldi prophecy |
E713881
|
entity |
| Predicate | centralCharacterForetold |
P45541
|
FINISHED |
| Object | Sydney Bristow |
—
|
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: Sydney Bristow | Statement: [Rambaldi prophecy, centralCharacterForetold, Sydney Bristow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralCharacterForetold Context triple: [Rambaldi prophecy, centralCharacterForetold, Sydney Bristow]
-
A.
laterMainCharacterOf
Indicates that one entity becomes the main character of a work at a later point in time, succeeding another main character.
-
B.
storyCharacterizedAs
Indicates that a story is described, portrayed, or defined as having a particular quality, style, or attribute.
-
C.
narrativeCharacter
chosen
Indicates that one entity functions as a character within the narrative or story associated with another entity.
-
D.
protagonistBasedOn
Indicates that a fictional work’s main character is modeled on, inspired by, or derived from a particular real or fictional person or entity.
-
E.
mainCharactersAre
Indicates that the specified entities serve as the primary or central characters in a narrative or work.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 27, 2026, 11:38 p.m.