Triple
T35779823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 747-400F |
E1034405
|
entity |
| Predicate | mainDeckSideCargoDoor |
P183660
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Boeing 747-400F, mainDeckSideCargoDoor, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDeckSideCargoDoor Context triple: [Boeing 747-400F, mainDeckSideCargoDoor, yes]
-
A.
hasCargoDoorVariant
Indicates that one entity is a specific cargo-door-equipped version or configuration variant of another entity.
-
B.
hasCargoAccess
Indicates that an entity has the ability or permission to access a designated cargo area or its contents.
-
C.
hasDoorSide
Indicates that one entity represents a specific side or face of a door in relation to another entity.
-
D.
hasCargoHold
Indicates that something possesses a dedicated space or compartment for storing or transporting cargo.
-
E.
lowerDeckCargoPositions
Indicates the specific locations or slots designated for storing cargo in the lower deck area.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1feb5a48190bfc05dd6110ef41f |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a162672481909773f8383d91159a |
completed | May 3, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:06 p.m.