Triple
T35779824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 747-400F |
E1034405
|
entity |
| Predicate | upperDeckLength |
P184103
|
FINISHED |
| Object | shortened compared to 747-400 passenger version |
—
|
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: shortened compared to 747-400 passenger version | Statement: [Boeing 747-400F, upperDeckLength, shortened compared to 747-400 passenger version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperDeckLength Context triple: [Boeing 747-400F, upperDeckLength, shortened compared to 747-400 passenger version]
-
A.
upperDeckUsedFor
Indicates that the upper deck of an object or structure is utilized for a specified purpose or activity.
-
B.
deckNumber
Indicates the specific deck or floor level associated with an entity within a multi-level structure or vehicle.
-
C.
upperDeckDirection
Indicates the direction or orientation associated with the upper deck relative to a reference point or structure.
-
D.
numberOfDecks
Indicates the quantity of decks associated with or contained in an entity.
-
E.
numberOfBoosters
Indicates the quantity of booster units associated with or used by an entity.
- 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_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.