Triple
T10780568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INS Hansa |
E254307
|
entity |
| Predicate | hasIataCode |
P2569
|
FINISHED |
| Object | GOI |
E886366
|
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: GOI | Statement: [INS Hansa, hasIataCode, GOI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GOI Context triple: [INS Hansa, hasIataCode, GOI]
-
A.
GOI
GOI is the station code for General Osório, a major Rio de Janeiro Metro station serving the Ipanema area.
-
B.
GOI
chosen
GOI is the IATA airport code for Goa International Airport, the main commercial airport serving the Indian state of Goa.
-
C.
GOA
GOA is the IATA airport code for Genoa Cristoforo Colombo Airport, the main international airport serving the city of Genoa in Italy.
-
D.
Goa
Goa is a coastal state on India’s western shore known for its beaches, distinctive blend of Indian and Portuguese heritage, and vibrant tourism industry.
-
E.
Bhopas
Bhopas are traditional Rajasthani priest-singers and storytellers who perform epic narratives and devotional songs, often accompanied by instruments like the ektara.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732c384bc81908f503f3a2e0503a4 |
completed | April 9, 2026, 5:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de84c925088190922b9979cf77d01b |
completed | April 14, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:17 p.m.