Triple
T32326947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strange Relations |
E825939
|
entity |
| Predicate | hasTimePeriodOfStories |
P94706
|
FINISHED |
| Object | future |
—
|
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: future | Statement: [Strange Relations, hasTimePeriodOfStories, future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimePeriodOfStories Context triple: [Strange Relations, hasTimePeriodOfStories, future]
-
A.
hasTimeInStory
Indicates that a story element, event, or entity occurs or is present during a specific time or time interval within the narrative.
-
B.
timePeriodOfPrimaryStories
chosen
Indicates the time period during which the primary stories or main narrative events of something (e.g., a work or series) take place.
-
C.
numberOfStories
Indicates the total count of levels or floors that a structure or building has.
-
D.
yearsActiveInStory
Indicates the span of years during which the entity is active or participates within the context of the story.
-
E.
hasPeriodTitles
Indicates that an entity is associated with one or more titles that apply specifically to a defined time period.
- 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 12:47 a.m.