Triple
T979522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Handley Page O/400 |
E21134
|
entity |
| Predicate | enginePlacement |
P22132
|
FINISHED |
| Object | tractor nacelles between wings |
—
|
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: tractor nacelles between wings | Statement: [Handley Page O/400, enginePlacement, tractor nacelles between wings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enginePlacement Context triple: [Handley Page O/400, enginePlacement, tractor nacelles between wings]
-
A.
batteryPlacement
Indicates the spatial or positional relationship specifying where a battery is located or installed relative to another object or system.
-
B.
powertrainLocation
Indicates the physical placement or mounting position of a vehicle’s powertrain relative to the rest of the vehicle.
-
C.
availableEngineDisplacement
Indicates the range or specific values of engine displacement that are offered or applicable for a given entity.
-
D.
engineDisplacement
Indicates the total volume swept by all the pistons inside an engine’s cylinders during one complete cycle.
-
E.
engineSupplier
Indicates a relationship where one entity supplies or provides engines to another entity.
- 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b479e8f081908183448c36244e1f |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a8a3b08190b4538e119b13f7f5 |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b344f6f48190ba03ce593c94176b |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:40 p.m.