Triple
T35779847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 747-400F |
E1034405
|
entity |
| Predicate | cargoLoadingSystem |
P89809
|
FINISHED |
| Object | powered roller system |
—
|
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: powered roller system | Statement: [Boeing 747-400F, cargoLoadingSystem, powered roller system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoLoadingSystem Context triple: [Boeing 747-400F, cargoLoadingSystem, powered roller system]
-
A.
cargoLoading
Indicates the action or process of placing cargo onto a vehicle, vessel, or other transport medium for shipment or movement.
-
B.
cargoSystem
chosen
Indicates a relationship where an entity is part of, managed by, or associated with a cargo-handling or cargo-management system.
-
C.
cargoOperations
Indicates the handling, movement, and management of cargo during loading, unloading, transfer, or storage activities.
-
D.
vehicleLoadingMethod
Indicates the method or process by which a vehicle is loaded with goods, passengers, or other cargo.
-
E.
cargoAccess
Indicates that an entity has permission or capability to access, enter, or interact with a cargo area or cargo-related contents.
- 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_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. |
Created at: May 3, 2026, 4:06 p.m.