Triple
T19645006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banks of the Ohio |
E471650
|
entity |
| Predicate | hasFirstPersonNarrator |
P125278
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Banks of the Ohio, hasFirstPersonNarrator, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstPersonNarrator Context triple: [Banks of the Ohio, hasFirstPersonNarrator, true]
-
A.
usesFirstPersonNarrator
chosen
Indicates that a narrative work is told from the perspective of an "I" character who is part of the story.
-
B.
narrativePerspective
Indicates the point of view or vantage from which a narrative is told, specifying the relationship between the storyteller and the events being described.
-
C.
notPointOfViewNarratorIn
Indicates that the referenced entity does not serve as the point-of-view narrator within the specified narrative context.
-
D.
hasCoNarrator
Indicates that two or more entities share the role of narrating the same work, event, or story together.
-
E.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6412452d481908b6946cad3c411d5 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.