Triple
T6978646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syracuse Hancock International Airport |
E161779
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | SYR |
E61249
|
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: SYR | Statement: [Syracuse Hancock International Airport, IATAcode, SYR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SYR Context triple: [Syracuse Hancock International Airport, IATAcode, SYR]
-
A.
SYR
chosen
SYR is the three-letter ISO 3166-1 alpha-3 country code representing the Middle Eastern nation of Syria.
-
B.
SY
SY is a UK postcode area covering Shrewsbury and surrounding parts of Shropshire and nearby counties in western England and the Welsh border region.
-
C.
Sy
Sy is a Diameter-based interface in telecommunications networks used for policy and charging control between the PCRF and online charging systems.
-
D.
SYP
SYP is the ISO 4217 currency code for the Syrian pound, the official monetary unit of Syria.
-
E.
Syrkin
Syrkin is a Jewish surname most notably associated with Nachman Syrkin, a pioneering theorist of socialist Zionism.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db6aa6188190af7656ff4d0e3230 |
completed | March 27, 2026, 7:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c761b614e88190877455edd5f64cf1 |
completed | March 28, 2026, 5:05 a.m. |
Created at: March 27, 2026, 2:31 p.m.