Triple
T7785450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isla Verde International Airport |
E187230
|
entity |
| Predicate | ICAOCode |
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: [Isla Verde International Airport, ICAOCode, TJSJ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TJSJ Context triple: [Isla Verde International Airport, ICAOCode, 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.
TJT
TJT is the time zone used in Tajikistan, corresponding to Tajikistan Time (UTC+5).
-
C.
tj
tj is the GitHub username of TJ Holowaychuk, a prolific open-source developer known for creating popular Node.js and Go tools and frameworks.
-
D.
SJJ
SJJ is the three-letter IATA airport code for Sarajevo International Airport, the main airport serving Bosnia and Herzegovina’s capital city.
-
E.
TIJ
TIJ is the IATA airport code for Tijuana International Airport in Tijuana, Mexico.
- 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_69ca82af2d2c8190963861f5e0b8bf21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cadf22d9b4819081b877c751204a22 |
completed | March 30, 2026, 8:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69caf604715081909eed614cbadb8db6 |
completed | March 30, 2026, 10:15 p.m. |
Created at: March 30, 2026, 4:23 p.m.