Triple
T33118456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorian |
E847522
|
entity |
| Predicate | hasProcessingSpeed |
P9334
|
FINISHED |
| Object | Enhanced |
—
|
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: Enhanced | Statement: [Dorian, hasProcessingSpeed, Enhanced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProcessingSpeed Context triple: [Dorian, hasProcessingSpeed, Enhanced]
-
A.
hasClockSpeed
chosen
Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
-
B.
topOperatingSpeed
Indicates the maximum speed at which an entity is designed or allowed to operate under normal conditions.
-
C.
hasServiceSpeed
Indicates that an entity provides a service operating at a specified speed or performance rate.
-
D.
operatingSpeedComparedToContemporaries
Indicates how an entity’s operating speed compares relative to other similar entities from the same time period.
-
E.
hasProcessingUnits
Indicates that an entity is equipped with or contains one or more processing units (such as CPUs, GPUs, or similar computational components).
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a016b2629c48190befb10581560d58f |
completed | May 11, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a0167d5a2088190a68dbd2b87f73e80 |
completed | May 11, 2026, 5:23 a.m. |
Created at: May 1, 2026, 1:27 a.m.