Triple
T2008479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midas Run |
E43638
|
entity |
| Predicate | runtimeApproximate |
P31999
|
FINISHED |
| Object | approximately 100 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 100 minutes | Statement: [Midas Run, runtimeApproximate, approximately 100 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runtimeApproximate Context triple: [Midas Run, runtimeApproximate, approximately 100 minutes]
-
A.
runtimeApprox
chosen
Indicates an approximate or estimated duration of time that something (such as a process, program, or event) takes to run or complete.
-
B.
approximateSize
Indicates that one entity has a size that is roughly or approximately equal to the size of another entity.
-
C.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
D.
approximateCapacity
Indicates that one entity has an estimated or rough capacity value relative to another or to a specified measure.
-
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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb89aca908190b8b659af65afdf6f |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.