Triple
T16741351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CH-47F Chinook |
E406840
|
entity |
| Predicate | doorGunPositions |
P124459
|
FINISHED |
| Object | forward cabin door |
—
|
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: forward cabin door | Statement: [CH-47F Chinook, doorGunPositions, forward cabin door]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doorGunPositions Context triple: [CH-47F Chinook, doorGunPositions, forward cabin door]
-
A.
doorLocation
Indicates the spatial position or placement of a door relative to a reference structure or area.
-
B.
gateOrientation
Indicates the directional alignment or facing direction of a gate relative to a reference frame or coordinate system.
-
C.
doorConfiguration
Indicates how a door is arranged or set up in relation to its frame, opening direction, and operational characteristics.
-
D.
doorSymbol
Indicates a symbolic representation that denotes or marks the presence or concept of a door.
-
E.
hasDoorGuard
Indicates that an entity has another entity serving as a guard for its door or entrance.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3e87348190acaf7c40e8f8b566 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:21 a.m.