Triple
T3943230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milan–San Remo |
E92083
|
entity |
| Predicate | typicalFinishTime |
P6833
|
FINISHED |
| Object | late afternoon |
—
|
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: late afternoon | Statement: [Milan–San Remo, typicalFinishTime, late afternoon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFinishTime Context triple: [Milan–San Remo, typicalFinishTime, late afternoon]
-
A.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
B.
typicalCompletionTimeInWeeks
Indicates the usual number of weeks it takes to complete the associated task, process, or activity.
-
C.
typicalTimes
chosen
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
D.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
E.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee764235081909309b3c982f322a9 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.