Triple
T19664075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Too Far to Go |
E472155
|
entity |
| Predicate | containsStoriesAbout |
P6847
|
FINISHED |
| Object | marital conflict |
—
|
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: marital conflict | Statement: [Too Far to Go, containsStoriesAbout, marital conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsStoriesAbout Context triple: [Too Far to Go, containsStoriesAbout, marital conflict]
-
A.
containsNarrativeOf
chosen
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
B.
originStoryIncludes
Indicates that an entity’s origin story contains, involves, or features the referenced element as a component or part of that backstory.
-
C.
sourceOfStories
Indicates that one entity serves as the origin or provider of stories for another entity.
-
D.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
E.
storylinesInclude
Indicates that certain storylines are contained within, or form part of, a larger narrative or collection of narratives.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6416749d48190b141a6acd20c9694 |
completed | April 20, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.