Triple
T25845976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terry |
E651068
|
entity |
| Predicate | importanceInStory |
P26062
|
FINISHED |
| Object | pivotal period in narrative |
—
|
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: pivotal period in narrative | Statement: [Terry, importanceInStory, pivotal period in narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importanceInStory Context triple: [Terry, importanceInStory, pivotal period in narrative]
-
A.
narrativeImportance
chosen
Indicates the degree to which an entity or event is central, influential, or essential within the structure and progression of a narrative.
-
B.
importanceToSeries
Indicates how crucial or significant an entity is within the context of a particular series.
-
C.
popularityInStory
Indicates how widely recognized, admired, or socially favored an entity is within the context of a specific story or narrative.
-
D.
importanceInEvent
Indicates the degree to which an entity plays a significant or central role within a particular event.
-
E.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 22, 2026, 7:52 a.m.