Triple
T27289603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockheed XP-49 |
E688580
|
entity |
| Predicate | intendedEngineConfiguration |
P126273
|
FINISHED |
| Object | liquid-cooled V-12 |
—
|
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: liquid-cooled V-12 | Statement: [Lockheed XP-49, intendedEngineConfiguration, liquid-cooled V-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedEngineConfiguration Context triple: [Lockheed XP-49, intendedEngineConfiguration, liquid-cooled V-12]
-
A.
intendedEngineType
chosen
Indicates that an entity is designed or specified to use a particular type of engine.
-
B.
engineConfigurationSupport
Indicates that one entity provides or defines support for a particular engine configuration of another entity.
-
C.
plannedEngineModel
Indicates that an engine model has been selected or designated as the one intended to be used or implemented in a future plan or configuration.
-
D.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
E.
combustionEngineConfiguration
Indicates the specific arrangement and setup of components and operating parameters within a combustion engine.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 11:14 a.m.