Triple
T18709793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ralph |
E457472
|
entity |
| Predicate | storyCentrality |
P35676
|
FINISHED |
| Object | main character |
—
|
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: main character | Statement: [Ralph, storyCentrality, main character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyCentrality Context triple: [Ralph, storyCentrality, main character]
-
A.
storyElement
chosen
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
B.
coreNarrative
Indicates the primary storyline or central sequence of events that forms the main thread of a narrative.
-
C.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
D.
narrativeConnection
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.
-
E.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5671a3c8c81909466bf5d81477a37 |
completed | April 19, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69e478e0889c8190a118d67b200ce8ef |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.