Triple
T1228431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luis Muñoz Marín International Airport |
E26379
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | TJSJ |
E26380
|
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: TJSJ | Statement: [Luis Muñoz Marín International Airport, ICAO code, TJSJ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TJSJ Context triple: [Luis Muñoz Marín International Airport, ICAO code, TJSJ]
-
A.
TJSJ
chosen
TJSJ is the ICAO airport code for Luis Muñoz Marín International Airport, the main commercial airport serving San Juan, Puerto Rico.
-
B.
TIJ
TIJ is the IATA airport code for Tijuana International Airport in Tijuana, Mexico.
-
C.
TJ
TJ is the two-letter ISO 3166-1 alpha-2 country code assigned to Tajikistan.
-
D.
TJCP
TJCP is the ICAO airport code assigned to Benjamin Rivera Noriega Airport in Puerto Rico.
-
E.
JST
JST is the time zone used throughout Japan, nine hours ahead of Coordinated Universal Time (UTC+9).
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be3c5d4c819087f9e9e37204c3be |
completed | March 1, 2026, 10:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac8a1242048190ba6ffcaacc4ca5d5 |
completed | March 7, 2026, 8:26 p.m. |
Created at: March 1, 2026, 7:47 p.m.