Triple
T3350178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liège–Bastogne–Liège 1966 |
E70471
|
entity |
| Predicate | totalTime |
P43134
|
FINISHED |
| Object | 6h 58m 00s |
—
|
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: 6h 58m 00s | Statement: [Liège–Bastogne–Liège 1966, totalTime, 6h 58m 00s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalTime Context triple: [Liège–Bastogne–Liège 1966, totalTime, 6h 58m 00s]
-
A.
durationTotal
chosen
Indicates the overall length of time for which an event, process, or state persists, typically aggregating all its constituent durations.
-
B.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
C.
actualDuration
Indicates the real amount of time that an event, process, or activity actually took to complete, as opposed to its planned or estimated duration.
-
D.
spentTimeIn
Indicates that an entity has spent a certain amount or period of time in a particular place or context.
-
E.
runtimeMinutes
Indicates the total duration of something, typically a media work or process, measured in minutes.
- 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_69ad85a4ef7c8190a29e2bbd6fa454e4 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb21f3ae48190a33530712da01bc3 |
completed | March 8, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.