Triple
T15958801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Anderton |
E387003
|
entity |
| Predicate | storyQuestion |
P120601
|
FINISHED |
| Object | Can the future be changed? |
—
|
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: Can the future be changed? | Statement: [John Anderton, storyQuestion, Can the future be changed?]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyQuestion Context triple: [John Anderton, storyQuestion, Can the future be changed?]
-
A.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
B.
storyTitle
Indicates that one entity is the title assigned to a story associated with another entity.
-
C.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
D.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
E.
storyTime
Indicates that one entity is narrating or sharing a story with another entity, typically in a designated or scheduled period for storytelling.
- F. None of above. chosen
Provenance (4 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e173af801c8190bfc0f602831bb594 |
completed | April 16, 2026, 11:41 p.m. |
Created at: April 10, 2026, 4:53 a.m.