Triple
T31806642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vexations |
E811889
|
entity |
| Predicate | approximateTotalDuration |
P4874
|
FINISHED |
| Object | 18 hours |
—
|
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: 18 hours | Statement: [Vexations, approximateTotalDuration, 18 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateTotalDuration Context triple: [Vexations, approximateTotalDuration, 18 hours]
-
A.
hasApproximateDuration
chosen
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
B.
durationTotal
Indicates the overall length of time for which an event, process, or state persists, typically aggregating all its constituent durations.
-
C.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
D.
lengthInMinutes
Indicates the duration of something expressed as a number of minutes.
-
E.
commonDuration
Indicates that two or more events, actions, or states share the same length of time.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: April 30, 2026, 11:43 p.m.