Triple
T30428620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mac Pro (2019) |
E774098
|
entity |
| Predicate | hasAfterburnerOption |
P170220
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mac Pro (2019), hasAfterburnerOption, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAfterburnerOption Context triple: [Mac Pro (2019), hasAfterburnerOption, yes]
-
A.
hasAfterburner
Indicates that one entity is equipped with, or possesses, an afterburner system in relation to another entity or context.
-
B.
hasTurbocharger
Indicates that an engine or vehicle is equipped with a turbocharger that boosts its air intake and performance.
-
C.
turbochargedEngineAvailable
Indicates that a turbocharged engine option is offered or can be equipped for the given vehicle or model.
-
D.
turbochargedVariant
Indicates that one entity is a turbocharged version or configuration of another entity.
-
E.
AfterburnType
Indicates that one event, state, or process occurs as a subsequent or follow-up phase (an "afterburn") relative to another, typically extending or intensifying its effects.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b121eac81909e90416207bc1157 |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f68a160374819084d720985f800dfc |
completed | May 2, 2026, 11:34 p.m. |
Created at: April 29, 2026, 8:06 p.m.