Triple
T15187536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sella Ronda ski circuit |
E362914
|
entity |
| Predicate | canBeCompletedIn |
P17474
|
FINISHED |
| Object | one 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: one day | Statement: [Sella Ronda ski circuit, canBeCompletedIn, one day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeCompletedIn Context triple: [Sella Ronda ski circuit, canBeCompletedIn, one day]
-
A.
timeToComplete
chosen
Indicates the duration required for an entity or process to be fully completed.
-
B.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
C.
isComplete
Indicates that an action, process, or object has finished all required steps or reached its final state with nothing remaining to be done.
-
D.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
-
E.
isCompleteFor
Indicates that one entity fully satisfies or finishes the requirements, scope, or intended purpose of another entity.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0067995fc8190b048f15086bd42f0 |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.