Triple
T17426603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MASCOT |
E423753
|
entity |
| Predicate | actualOperatingTime |
P40756
|
FINISHED |
| Object | over 17 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: over 17 hours | Statement: [MASCOT, actualOperatingTime, over 17 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualOperatingTime Context triple: [MASCOT, actualOperatingTime, over 17 hours]
-
A.
actualDuration
chosen
Indicates the real amount of time that an event, process, or activity actually took to complete, as opposed to its planned or estimated duration.
-
B.
operatesAtTime
Indicates that an action, process, or system is functioning or active during a specified time or time interval.
-
C.
operatedAt
Indicates that an operation, procedure, or activity was performed at a specific location or facility.
-
D.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
E.
operatesAllTimes
Indicates that the action, service, or process is continuously in operation at all times without interruption.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e448fcbf54819091babed0b9b05716 |
completed | April 19, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b030eac481909b8402719cc3102e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.