Triple
T12413119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Concertgebouw Orchestra |
E296567
|
entity |
| Predicate | hasOwnLabel |
P20703
|
FINISHED |
| Object | RCO Live |
E296572
|
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: RCO Live | Statement: [Royal Concertgebouw Orchestra, hasOwnLabel, RCO Live]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RCO Live Context triple: [Royal Concertgebouw Orchestra, hasOwnLabel, RCO Live]
-
A.
RCO Live
chosen
RCO Live is the in-house record label of the Royal Concertgebouw Orchestra, dedicated to releasing high-quality recordings of the orchestra’s performances.
-
B.
REO Royale
The REO Royale was a luxury automobile produced in the early 1930s, recognized for its advanced engineering, elegant styling, and status as the flagship model of the REO Motor Car Company.
-
C.
RCO
RCO is the commonly used abbreviation for the Royal Concertgebouw Orchestra, one of the world’s leading symphony orchestras based in Amsterdam.
-
D.
Rave On
"Rave On" is a classic 1958 rock and roll song, best known for its energetic performance by pioneering musician Buddy Holly.
-
E.
Life Live
Life Live is a music release by the hardcore punk band Hardline.
- 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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94d6b0f9c8190813b6fe3f97570ac |
completed | April 10, 2026, 7:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f63f002b7c81909ee9d4ea3ea6d5f2 |
completed | May 2, 2026, 6:14 p.m. |
Created at: April 8, 2026, 9:55 p.m.