Triple
T5049215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Philharmonic Orchestra |
E113742
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | RPO |
E488277
|
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: RPO | Statement: [Royal Philharmonic Orchestra, hasAbbreviation, RPO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RPO Context triple: [Royal Philharmonic Orchestra, hasAbbreviation, RPO]
-
A.
RPO
chosen
RPO is the commonly used abbreviation for the Royal Philharmonic Orchestra, one of the major symphony orchestras based in London, England.
-
B.
ROP
ROP is the IATA airport code for Rota International Airport, a public airport serving the island of Rota in the Northern Mariana Islands.
-
C.
RP
RP is the prestige British English accent traditionally associated with educated speakers and national broadcasters in the United Kingdom.
-
D.
RP
RP is the former IATA airline designator assigned to Chautauqua Airlines, a now-defunct regional carrier in the United States.
-
E.
RE
RE is the common abbreviation for the British Army’s Corps of Royal Engineers, responsible for military engineering and technical support.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bea47e5ba0819088217a9ad3ce2b0a |
completed | March 21, 2026, 2 p.m. |
Created at: March 20, 2026, 1:37 p.m.