Triple
T37399681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QB VII |
E928958
|
entity |
| Predicate | runtimeTotal |
P31999
|
FINISHED |
| Object | approximately 390 minutes |
—
|
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: approximately 390 minutes | Statement: [QB VII, runtimeTotal, approximately 390 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runtimeTotal Context triple: [QB VII, runtimeTotal, approximately 390 minutes]
-
A.
runsTotal
Indicates the total number of runs accumulated or recorded for an entity over a specified period or context.
-
B.
runtimeApprox
chosen
Indicates an approximate or estimated duration of time that something (such as a process, program, or event) takes to run or complete.
-
C.
durationTotal
Indicates the overall length of time for which an event, process, or state persists, typically aggregating all its constituent durations.
-
D.
commonTotalLength
Indicates that the entities share the same overall measured length.
-
E.
totalSystemLength
Indicates the complete measured length of an entire system, aggregating all its relevant components or segments.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.