Triple
T15816325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maddux Air Lines |
E383486
|
entity |
| Predicate | cargoTransport |
P87144
|
FINISHED |
| Object | no significant cargo operations known |
—
|
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: no significant cargo operations known | Statement: [Maddux Air Lines, cargoTransport, no significant cargo operations known]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoTransport Context triple: [Maddux Air Lines, cargoTransport, no significant cargo operations known]
-
A.
cargoSystem
Indicates a relationship where an entity is part of, managed by, or associated with a cargo-handling or cargo-management system.
-
B.
cargoAccess
Indicates that an entity has permission or capability to access, enter, or interact with a cargo area or cargo-related contents.
-
C.
cargoLoading
Indicates the action or process of placing cargo onto a vehicle, vessel, or other transport medium for shipment or movement.
-
D.
cargoOperations
chosen
Indicates the handling, movement, and management of cargo during loading, unloading, transfer, or storage activities.
-
E.
railCarries
Indicates that a rail or railway system transports or conveys a specified entity from one place to another.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a306a48190840adc49df2c26c5 |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.