Triple
T5362322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porbandar |
E103049
|
entity |
| Predicate | airportIATACode |
P418
|
FINISHED |
| Object | PBD |
E109351
|
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: PBD | Statement: [Porbandar, airportIATACode, PBD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PBD Context triple: [Porbandar, airportIATACode, PBD]
-
A.
PBD
chosen
PBD is the IATA airport code for Porbandar Airport, a domestic airport serving the city of Porbandar in the Indian state of Gujarat.
-
B.
PB
PB is the post-nominal abbreviation used to denote recipients of the Padma Bhushan, one of India’s highest civilian honors.
-
C.
PDS
PDS is the IATA airport code for the international airport serving Piedras Negras in the Mexican state of Coahuila.
-
D.
PDS
PDS was a democratic socialist political party in Germany that emerged from the former East German ruling party and later became part of The Left (Die Linke).
-
E.
PDS
PDS is an abbreviation used for the Social Democratic Party of Switzerland, a major center-left political party in Switzerland.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865a0bb081909579cfe7c7974075 |
completed | March 20, 2026, 5:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf21ef7acc8190aa7ff990a04ff09c |
completed | March 21, 2026, 10:55 p.m. |
Created at: March 20, 2026, 2:02 p.m.