Triple
T8767136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waverley |
E208364
|
entity |
| Predicate | timeGapIndicatedBySubtitle |
P79788
|
FINISHED |
| Object | sixty years |
—
|
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: sixty years | Statement: [Waverley, timeGapIndicatedBySubtitle, sixty years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeGapIndicatedBySubtitle Context triple: [Waverley, timeGapIndicatedBySubtitle, sixty years]
-
A.
hasSubtitles
Indicates that one media item provides subtitle text or tracks that accompany another media item or its audio content.
-
B.
timeInterpretation
Indicates how a given temporal expression or event should be understood or interpreted in terms of time (e.g., its reference point, scope, or temporal role).
-
C.
hasTimeIndication
chosen
Indicates that something includes, specifies, or is associated with a particular time-related indication (such as a timestamp, time period, or temporal marker).
-
D.
timeIntervalLength
Indicates the duration or length of a specified time interval.
-
E.
timeBehind
Indicates that one entity occurs or is positioned later in time than another, lagging behind it on a temporal scale.
- 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5eeae70c8190adc2bc2846da0fbf |
completed | March 31, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:41 p.m.