Triple
T19414995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kawasaki C-X program |
E485688
|
entity |
| Predicate | cargoRole |
P7949
|
FINISHED |
| Object | military logistics transport |
—
|
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: military logistics transport | Statement: [Kawasaki C-X program, cargoRole, military logistics transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoRole Context triple: [Kawasaki C-X program, cargoRole, military logistics transport]
-
A.
hasCargoRole
Indicates that an entity participates in a cargo-related capacity or function within a transport, shipment, or logistics context.
-
B.
cargoAccess
Indicates that an entity has permission or capability to access, enter, or interact with a cargo area or cargo-related contents.
-
C.
cargoSystem
Indicates a relationship where an entity is part of, managed by, or associated with a cargo-handling or cargo-management system.
-
D.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
E.
transportRole
chosen
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af90758819088999d98d270011a |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.