Triple
T37421358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colt Vahn |
E929860
|
entity |
| Predicate | timeStructureOfStory |
P25625
|
FINISHED |
| Object | repeating day |
—
|
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: repeating day | Statement: [Colt Vahn, timeStructureOfStory, repeating day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeStructureOfStory Context triple: [Colt Vahn, timeStructureOfStory, repeating day]
-
A.
timeOfNarrative
Indicates the specific time or period during which the events of a narrative are set or unfold.
-
B.
timeStructure
chosen
Indicates that one entity defines, constrains, or organizes the temporal framework or schedule within which another entity exists or operates.
-
C.
storyTime
Indicates that one entity is narrating or sharing a story with another entity, typically in a designated or scheduled period for storytelling.
-
D.
narrativeTimeSpanHours
Indicates the duration of a narrative or story event measured in hours.
-
E.
storyTimeContext
Indicates the situational setting or circumstances in which a story is told or takes place, such as time, place, or surrounding conditions.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.