Triple
T8471538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Control Panels (classic Mac OS) |
E200290
|
entity |
| Predicate | configurationTime |
P2093
|
FINISHED |
| Object | runtime |
—
|
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: runtime | Statement: [Control Panels (classic Mac OS), configurationTime, runtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationTime Context triple: [Control Panels (classic Mac OS), configurationTime, runtime]
-
A.
deploymentTime
Indicates the point in time at which something is deployed, initiated, or put into operation.
-
B.
configuration
chosen
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
-
C.
bootTimeCharacteristic
Indicates the duration or properties of the time it takes a system or device to start up from an inactive state.
-
D.
timeOfSetting
Indicates the specific time at which an event, object, or phenomenon is set, scheduled, or takes place.
-
E.
constructionTime
Indicates the duration or specific point in time required to construct or build an entity.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f3a81881908f20514579945ffa |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.