Triple
T10873328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eros Airport |
E256711
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | ERS |
E120165
|
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: ERS | Statement: [Eros Airport, IATAcode, ERS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ERS Context triple: [Eros Airport, IATAcode, ERS]
-
A.
ERS
chosen
ERS is the principal economic and social science research agency of the U.S. Department of Agriculture, providing data and analysis on agriculture, food, the environment, and rural development.
-
B.
ER
ER is the vehicle registration code assigned to the German city of Erlangen in the state of Bavaria.
-
C.
ER
ER is the commonly used abbreviation for United Russia, the dominant ruling political party in the Russian Federation.
-
D.
ER
ER is a critically acclaimed American medical drama television series that follows the personal and professional lives of staff in a busy Chicago emergency room.
-
E.
ER
ER is the zone code for Eastern Railway, one of the major railway zones of Indian Railways headquartered in Kolkata.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751891b508190959784f212e06acb |
completed | April 9, 2026, 7:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dff7ddafc48190824c133bb33b9efe |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 8, 2026, 9:21 p.m.