Triple
T35779845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 747-400F |
E1034405
|
entity |
| Predicate | mainDeckFloorStrength |
P184104
|
FINISHED |
| Object | reinforced for heavy cargo |
—
|
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: reinforced for heavy cargo | Statement: [Boeing 747-400F, mainDeckFloorStrength, reinforced for heavy cargo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDeckFloorStrength Context triple: [Boeing 747-400F, mainDeckFloorStrength, reinforced for heavy cargo]
-
A.
numberOfDeckPlanks
Indicates the quantity of deck planks associated with a given structure or object.
-
B.
observationDeckFloor
Indicates the specific floor or level of a building on which an observation deck is located.
-
C.
deckNumber
Indicates the specific deck or floor level associated with an entity within a multi-level structure or vehicle.
-
D.
impactFloorsApproximate
Indicates that one entity affects or influences another across an estimated or approximate number of floors or vertical levels.
-
E.
doorFloorLevel
Indicates that a door is located at or associated with a specific floor level within a building or structure.
- 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.