Triple
T1053385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing AH-64 Apache |
E22747
|
entity |
| Predicate | rotorDiameter |
P22940
|
FINISHED |
| Object | approximately 14.63 m |
—
|
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: approximately 14.63 m | Statement: [Boeing AH-64 Apache, rotorDiameter, approximately 14.63 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotorDiameter Context triple: [Boeing AH-64 Apache, rotorDiameter, approximately 14.63 m]
-
A.
fairingDiameter
Indicates the diameter measurement of a payload fairing used to enclose or protect an object.
-
B.
driverDiameter
Indicates the size of the circular cross-section of a driver component, typically measured as the distance across its widest point.
-
C.
coreStageDiameter
Indicates the diameter measurement of the central or primary stage of an object or system.
-
D.
propellerType
Indicates the specific kind or classification of propeller associated with an entity.
-
E.
approximateDiameter
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8b644088190a1f0f00f97941298 |
completed | March 1, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69a4b731e25c8190b5ea8466648c2c9a |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7da38888190a118ef20ce4ae9aa |
completed | March 1, 2026, 10:04 p.m. |
Created at: March 1, 2026, 7:42 p.m.