Triple
T28766983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mollie McDonald |
E726301
|
entity |
| Predicate | hasNarrativeConnection |
P51756
|
FINISHED |
| Object | Ewing Oil |
—
|
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: Ewing Oil | Statement: [Mollie McDonald, hasNarrativeConnection, Ewing Oil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNarrativeConnection Context triple: [Mollie McDonald, hasNarrativeConnection, Ewing Oil]
-
A.
narrativeConnection
chosen
Indicates a meaningful relationship between elements within a narrative, such as events, characters, or scenes, that links them in terms of plot, causality, or thematic continuity.
-
B.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
C.
hasNarrativeContext
Indicates that an entity is associated with, or situated within, a particular narrative or storytelling context that frames its meaning or role.
-
D.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
E.
hasNarrativeOrigin
Indicates that something originates from, is derived from, or is based on a particular narrative or story.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 28, 2026, 6:14 a.m.