Triple
T37343051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Encounter |
E927095
|
entity |
| Predicate | runTimeApprox |
P31999
|
FINISHED |
| Object | about two 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: about two hours | Statement: [The Encounter, runTimeApprox, about two hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runTimeApprox Context triple: [The Encounter, runTimeApprox, about two hours]
-
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.
runsApproximately
Indicates that an entity performs a running action in a manner that is close to, but not exactly matching, a specified time, distance, speed, or other running-related measure.
-
C.
typicalRuntimeRange
Indicates the usual lower and upper bounds of time typically required for an entity to run or complete its operation.
-
D.
approximateEstimation
Indicates an estimation relationship where one value or assessment is only roughly or closely, but not exactly, equal to another.
-
E.
runTimeSupport
Indicates that one entity provides or requires support for another entity during its execution at run 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.