Triple
T15287300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAJ |
E365433
|
entity |
| Predicate | represents |
P129
|
FINISHED |
| Object | Rajkot Airport |
E74212
|
NE 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: Rajkot Airport | Statement: [RAJ, represents, Rajkot Airport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rajkot Airport Context triple: [RAJ, represents, Rajkot Airport]
-
A.
Rajkot Airport
chosen
Rajkot Airport is a domestic airport serving the city of Rajkot and surrounding regions in the Indian state of Gujarat.
-
B.
Vadodara Airport
Vadodara Airport is a domestic airport in the city of Vadodara, India, serving as one of the key air transport hubs in the state of Gujarat.
-
C.
Kolhapur Airport
Kolhapur Airport is a regional airport in Maharashtra, India, serving the city of Kolhapur and its surrounding areas with domestic air connectivity.
-
D.
Bhavnagar airport
Bhavnagar Airport is a domestic airport in Gujarat, India, serving the city of Bhavnagar and its surrounding region with scheduled commercial flights.
-
E.
Kandla Airport
Kandla Airport is a domestic airport in Gujarat, India, serving the port city of Kandla and the nearby town of Gandhidham.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e551bb0819094db097285443740 |
completed | April 15, 2026, 10:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff0b39b6f88190ac9d6532e99fda31 |
completed | May 9, 2026, 10:23 a.m. |
Created at: April 10, 2026, 3:15 a.m.