Triple
T7980179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Core m3-8100Y |
E185550
|
entity |
| Predicate | supportsIntelTurboBoost |
P80133
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Intel Core m3-8100Y, supportsIntelTurboBoost, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsIntelTurboBoost Context triple: [Intel Core m3-8100Y, supportsIntelTurboBoost, true]
-
A.
hasClockSpeed
Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
-
B.
supportsBigLittleHybrid
Indicates that an entity is compatible with or enables operation using a big.LITTLE-style heterogeneous core or component configuration.
-
C.
supportsThunderbolt
Indicates that one entity provides compatibility with or the capability to use Thunderbolt technology for another entity.
-
D.
supportsDualProcessors
Indicates that an entity is capable of operating with or accommodating two processors simultaneously.
-
E.
turbochargedEngineAvailable
Indicates that a turbocharged engine option is offered or can be equipped for the given vehicle or model.
- F. None of above. chosen
Provenance (4 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c274ce48190854d389d43ce14b8 |
completed | March 31, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:14 p.m.