Triple
T29526269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G-VWOW |
E749076
|
entity |
| Predicate | hasWingPylon |
P32602
|
FINISHED |
| Object | left wing inboard hardpoint |
—
|
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: left wing inboard hardpoint | Statement: [G-VWOW, hasWingPylon, left wing inboard hardpoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWingPylon Context triple: [G-VWOW, hasWingPylon, left wing inboard hardpoint]
-
A.
hasWingConfiguration
Indicates how an entity’s wings are arranged, structured, or configured relative to its body or to each other.
-
B.
hasWingIn
Indicates that an entity possesses a wing that is located in or contained within another specified entity or structure.
-
C.
hasWingOf
Indicates that one entity possesses or is associated with the wing that belongs to another entity.
-
D.
hasArmedWing
Indicates that an entity maintains, controls, or is associated with an organized armed or military wing.
-
E.
hasPylon
chosen
Indicates that one entity possesses, includes, or is equipped with a pylon as part of its structure or configuration.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.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 28, 2026, 4:46 p.m.