Triple
T18508069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John "Sully" Sullivan |
E452250
|
entity |
| Predicate | focusOfStoryline |
P86548
|
FINISHED |
| Object | personal redemption |
—
|
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: personal redemption | Statement: [John "Sully" Sullivan, focusOfStoryline, personal redemption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusOfStoryline Context triple: [John "Sully" Sullivan, focusOfStoryline, personal redemption]
-
A.
focusOf
chosen
Indicates that one entity is the primary subject, target, or center of attention, activity, or interest for another entity.
-
B.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
C.
focusFeature
Indicates that one entity is the primary or emphasized feature, aspect, or attribute being highlighted or concentrated on in relation to another.
-
D.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
E.
focusPosition
Indicates the spatial or logical position at which attention, concentration, or processing is currently directed within a given context.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53344033c8190a0883aef56ba79c3 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.