Triple
T12975725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francisco Sá Carneiro Airport |
E321518
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | OPO |
E921502
|
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: OPO | Statement: [Francisco Sá Carneiro Airport, IATAcode, OPO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OPO Context triple: [Francisco Sá Carneiro Airport, IATAcode, OPO]
-
A.
OPO
OPO is the vehicle registration code assigned to the Polish city of Opole.
-
B.
OPO
chosen
OPO is the IATA airport code for Francisco Sá Carneiro Airport, the main international airport serving Porto, Portugal.
-
C.
Opo
The Opo are a small Nilotic ethnic group living primarily in the borderlands of western Ethiopia and South Sudan, known for their agro-pastoralist lifestyle and distinct language and culture.
-
D.
O-pa
O-pa is the commonly used abbreviation for Omaha Performing Arts, a major nonprofit organization that presents and supports live performing arts in Omaha, Nebraska.
-
E.
OPOJAZ
OPOJAZ was a pioneering Russian Formalist literary group in early 20th-century Petrograd that developed influential theories of literary form and technique.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e48c0208190bb7ec80780480b37 |
completed | April 10, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8ec821c81909398d8e02d69dcbf |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 8:37 p.m.