Triple
T3341498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajiv Gandhi International Airport |
E70269
|
entity |
| Predicate | cargoTerminal |
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: [Rajiv Gandhi International Airport, cargoTerminal, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoTerminal Context triple: [Rajiv Gandhi International Airport, cargoTerminal, yes]
-
A.
cargoTerminalPlanned
Indicates that a cargo terminal is intended or scheduled to be constructed, developed, or put into operation at a given location or facility.
-
B.
hasCargoTerminal
chosen
Indicates that a location or facility includes or is equipped with a cargo terminal for handling freight.
-
C.
cargoLoading
Indicates the action or process of placing cargo onto a vehicle, vessel, or other transport medium for shipment or movement.
-
D.
cargoAccess
Indicates that an entity has permission or capability to access, enter, or interact with a cargo area or cargo-related contents.
-
E.
cargo
Indicates that one entity is the goods or load being transported, carried, or shipped by another entity.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1c0ae44819091c851569eaf4565 |
completed | March 8, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.