Triple
T255830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Diego International Airport |
E5434
|
entity |
| Predicate | hasCargoService |
P2420
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [San Diego International Airport, hasCargoService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCargoService Context triple: [San Diego International Airport, hasCargoService, yes]
-
A.
hasCargoTerminal
chosen
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.
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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25d5669008190978bbd7308be11f7 |
completed | Feb. 28, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69a25b694c08819085bb4b256fa7736f |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.