Triple
T26383914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seasons of Love |
E663221
|
entity |
| Predicate | timeSpanReferenced |
P136808
|
FINISHED |
| Object | one year |
—
|
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: one year | Statement: [Seasons of Love, timeSpanReferenced, one year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSpanReferenced Context triple: [Seasons of Love, timeSpanReferenced, one year]
-
A.
timeSpanMentioned
chosen
Indicates that a specific duration or period of time is explicitly referenced in the context.
-
B.
timeSpanLinked
Indicates that two events, states, or intervals are connected or associated through a specific span of time between them.
-
C.
timeSpanIncludes
Indicates that one time span fully contains or covers the entire duration of another time span.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
timePeriodQualifier
Indicates how a time-related statement or value is further specified or constrained, such as by defining its scope, phase, or contextual condition within a broader 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610779e3481909bda4d2b1c5c4cb0 |
completed | May 2, 2026, 2:55 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:21 p.m.