Triple
T19733735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maestro Wilson Fonseca International Airport |
E473919
|
entity |
| Predicate | pushpinLabel |
P9248
|
FINISHED |
| Object | STM |
—
|
NE NERFINISHED |
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: STM | Statement: [Maestro Wilson Fonseca International Airport, pushpinLabel, STM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: STM Context triple: [Maestro Wilson Fonseca International Airport, pushpinLabel, STM]
-
A.
STM
STM is the public transit agency serving the city of Montreal, operating its bus and metro networks.
-
B.
STM
STM is the station code for Smithtown station, a Long Island Rail Road commuter rail stop in Smithtown, New York.
-
C.
STM
STM is the stock ticker symbol for STMicroelectronics, a major global semiconductor manufacturer.
-
D.
STM
STM is the Finnish Ministry of Social Affairs and Health, the government body responsible for national social welfare and health policy in Finland.
-
E.
STM
chosen
STM is the IATA airport code for Maestro Wilson Fonseca International Airport serving Santarém in the state of Pará, Brazil.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6515b4d308190af3be1787fa7c65b |
completed | April 20, 2026, 4:16 p.m. |
Created at: April 10, 2026, 1:47 p.m.