Triple
T317304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osaka International Airport |
E7734
|
entity |
| Predicate | hasCargoServices |
P11980
|
FINISHED |
| Object | limited domestic 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: limited domestic cargo | Statement: [Osaka International Airport, hasCargoServices, limited domestic cargo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCargoServices Context triple: [Osaka International Airport, hasCargoServices, limited domestic cargo]
-
A.
hasCargoTerminal
Indicates that a location or facility includes or is equipped with a cargo terminal for handling freight.
-
B.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
C.
hasGroundTransportation
Indicates that an entity provides, includes, or is connected to transportation services or options that operate on land (e.g., cars, buses, trains).
-
D.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
E.
hasBaggageSystem
Indicates that an entity is equipped with or utilizes a baggage handling system.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea65ca7081908093e6aaaf2d34f7 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e943f12c8190883854aeed974260 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea08878c8190a5e8a90f620a3888 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.