Triple
T23366419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilatus PC-12 |
E593335
|
entity |
| Predicate | cabinAccess |
P124919
|
FINISHED |
| Object | aft cargo 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: aft cargo door | Statement: [Pilatus PC-12, cabinAccess, aft cargo door]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cabinAccess Context triple: [Pilatus PC-12, cabinAccess, aft cargo door]
-
A.
interiorAccess
Indicates that one entity provides a way to enter or move within the inside space of another entity.
-
B.
hasCargoAccess
chosen
Indicates that an entity has the ability or permission to access a designated cargo area or its contents.
-
C.
passengerAccess
Indicates that a passenger is allowed to enter, use, or move through a particular vehicle, area, or transportation-related facility.
-
D.
hasDomeOrRoofAccess
Indicates that an entity has access to, or the ability to reach or use, a dome or roof area associated with another entity.
-
E.
cabinAbove
Indicates that one cabin is positioned vertically higher than another cabin.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0ac7494819082e98ac5632eba28 |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:31 p.m.