Triple
T34934913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summer People |
E1007539
|
entity |
| Predicate | hasRecurringCharacterFromSeries |
P201934
|
FINISHED |
| Object | Nick Adams stories |
E968861
|
NE 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: Nick Adams stories | Statement: [Summer People, hasRecurringCharacterFromSeries, Nick Adams stories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecurringCharacterFromSeries Context triple: [Summer People, hasRecurringCharacterFromSeries, Nick Adams stories]
-
A.
hasRecurringCharacters
chosen
Indicates that an entity (such as a work or series) features characters who appear repeatedly across multiple parts, episodes, or installments.
-
B.
isRecurringCharacter
Indicates that an entity appears repeatedly or regularly within a given narrative, series, or context rather than only once.
-
C.
recurringCharacterInSeason
Indicates that a character appears repeatedly across multiple episodes within a specific season of a series.
-
D.
hasRecurringCharacterFrom
Indicates that one work or series includes a character who also appears recurrently in another work or series.
-
E.
hasRecurringSeriesProtagonists
Indicates that a recurring series features one or more protagonists who appear repeatedly across its installments.
- F. None of above.
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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37b26447cc8190a75dcc83b3110ef5 |
completed | June 21, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.