Triple
T4614987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porbandar railway station |
E100846
|
entity |
| Predicate | stationCode |
P1289
|
FINISHED |
| Object | PBR |
E100846
|
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: PBR | Statement: [Porbandar railway station, stationCode, PBR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PBR Context triple: [Porbandar railway station, stationCode, PBR]
-
A.
PBR
chosen
PBR is the Indian Railways station code for Porbandar railway station in Gujarat, India.
-
B.
PBD
PBD is the IATA airport code for Porbandar Airport, a domestic airport serving the city of Porbandar in the Indian state of Gujarat.
-
C.
PB
PB is the post-nominal abbreviation used to denote recipients of the Padma Bhushan, one of India’s highest civilian honors.
-
D.
PPR
PPR is the commonly used abbreviation for Philadelphia Parks & Recreation, the municipal department that manages the city’s parks, recreation centers, and related public programs.
-
E.
PPR
PPR was the communist political party that led Poland in the final years of World War II and laid the foundations for the postwar socialist state.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59c3d9ec8190a50ef03627dc351d |
completed | March 20, 2026, 2:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdfa8da23881909ba4a70e9697f260 |
completed | March 21, 2026, 1:55 a.m. |
Created at: March 20, 2026, 1:12 p.m.