Triple
T31947246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owen Moore |
E815684
|
entity |
| Predicate | hasFlashbackScenesWith |
P66473
|
FINISHED |
| Object | Abby Anderson |
—
|
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: Abby Anderson | Statement: [Owen Moore, hasFlashbackScenesWith, Abby Anderson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlashbackScenesWith Context triple: [Owen Moore, hasFlashbackScenesWith, Abby Anderson]
-
A.
hasFlashbackStorylines
chosen
Indicates that the narrative includes scenes or sequences set in earlier time periods that reveal past events related to the main storyline.
-
B.
hasCutscenes
Indicates that the subject includes or features one or more non-interactive cinematic sequences (cutscenes).
-
C.
hasFlashforwardEpisodes
Indicates that the work includes one or more episodes featuring flashforwards, i.e., scenes set in a future time relative to the main narrative.
-
D.
hasLastSceneWith
Indicates that two entities share the same final scene or appearance together within a work or sequence.
-
E.
hasReenactments
Indicates that an event, scene, or situation is represented again through staged or dramatized performances.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 12:07 a.m.