Triple
T15036906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Canada Rouge |
E378499
|
entity |
| Predicate | ICAOCode |
P419
|
FINISHED |
| Object | ROU |
E793409
|
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: ROU | Statement: [Air Canada Rouge, ICAOCode, ROU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ROU Context triple: [Air Canada Rouge, ICAOCode, ROU]
-
A.
ROU
chosen
ROU is the three-letter international country code used to represent Romania in sports and other global contexts.
-
B.
RO
RO is the IATA airline designator assigned to TAROM, the flag carrier airline of Romania.
-
C.
RO
RO is the stock ticker symbol for Roche, the multinational Swiss healthcare and pharmaceutical company.
-
D.
RO
RO is the vehicle registration code used on license plates for vehicles registered in the Province of Rovigo in Italy.
-
E.
RO
RO is the vehicle registration code used on license plates for vehicles registered in the district of Rosenheim in Germany.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded82b29948190acda49cbec3f927a |
completed | April 15, 2026, 12:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe9ddfc13481909333690016650410 |
completed | May 9, 2026, 2:37 a.m. |
Created at: April 10, 2026, 2:59 a.m.