Triple
T21146071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z34 |
E521057
|
entity |
| Predicate | typicalEngineCode |
P44382
|
FINISHED |
| Object | VQ37VHR |
—
|
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: VQ37VHR | Statement: [Z34, typicalEngineCode, VQ37VHR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEngineCode Context triple: [Z34, typicalEngineCode, VQ37VHR]
-
A.
typicalEngine
Indicates that an entity is the standard or commonly used engine for another entity (such as a vehicle, device, or system).
-
B.
engineCode
chosen
Indicates a relationship where an entity is associated with a specific engine identification code or designation.
-
C.
originalEngineType
Indicates the type or category of engine that an entity was initially or first equipped with.
-
D.
developedEngine
Indicates that one entity created, designed, or engineered an engine for another entity or purpose.
-
E.
engineBase
Indicates that one entity serves as the foundational or primary engine upon which another engine or engine-related component is built or derived.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723fdc25481909d6648e09b069c41 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:58 p.m.