Triple
T15829562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilyushin Il-86 |
E383833
|
entity |
| Predicate | passengerDecks |
P119798
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Ilyushin Il-86, passengerDecks, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerDecks Context triple: [Ilyushin Il-86, passengerDecks, 1]
-
A.
hasVehicleDeck
Indicates that something (typically a vessel or structure) includes a dedicated deck or level designed for carrying or transporting vehicles.
-
B.
gunDecks
Indicates that one entity is equipped with, contains, or is associated with the gun decks of another entity, typically referring to the levels or platforms on a vessel where guns are mounted.
-
C.
mainDeckCargoPositions
Indicates the designated locations on a vessel’s main deck where cargo can be placed or secured.
-
D.
passengerSystem
Indicates a relationship where an entity functions as or belongs to a passenger-related system (such as a transport or service system designed for passengers).
-
E.
passengers
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e62aba8819090978801f4df73fe |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e007647f908190adb178c68c7bb7cf |
completed | April 15, 2026, 9:47 p.m. |
Created at: April 10, 2026, 4:49 a.m.