Triple
T381596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GMT900 |
E8690
|
entity |
| Predicate | engineCompatibility |
P5090
|
FINISHED |
| Object | V6 engines |
—
|
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: V6 engines | Statement: [GMT900, engineCompatibility, V6 engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineCompatibility Context triple: [GMT900, engineCompatibility, V6 engines]
-
A.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
-
B.
isBuiltFor
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
-
C.
backwardCompatibleWith
Indicates that one entity can correctly interpret, use, or function with data, interfaces, or behavior designed for an earlier version of another entity.
-
D.
supportedPlatform
chosen
Indicates that one entity (such as a system, application, or service) is compatible with and can operate on a particular platform.
-
E.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2e3d5c8190b358bd9fd6b16a14 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e96602188190b0cbc167f55a9237 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.