Triple
T32827088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karipur |
E839581
|
entity |
| Predicate | airportNameAtLocation |
P107376
|
FINISHED |
| Object | Calicut International Airport |
—
|
NE NERFINISHED |
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: Calicut International Airport | Statement: [Karipur, airportNameAtLocation, Calicut International Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportNameAtLocation Context triple: [Karipur, airportNameAtLocation, Calicut International Airport]
-
A.
airportLocatedNear
Indicates that an airport is situated close to a specified place or geographic feature.
-
B.
airportLocatedIn
Indicates that an airport is geographically situated within a specific administrative or territorial area.
-
C.
airportLocatedWithin
Indicates that an airport is geographically situated inside the boundaries of a specified area or region.
-
D.
associatedAirportLocalName
chosen
Indicates the local or native-language name of the airport that is associated with the given entity.
-
E.
airportLinkName
Indicates the name assigned to a transportation link or connection associated with an airport.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:16 a.m.