Triple
T12413101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Concertgebouw Orchestra |
E296567
|
entity |
| Predicate | receivedRoyalTitleIn |
P65823
|
FINISHED |
| Object | 1988 |
—
|
LITERAL 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: 1988 | Statement: [Royal Concertgebouw Orchestra, receivedRoyalTitleIn, 1988]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedRoyalTitleIn Context triple: [Royal Concertgebouw Orchestra, receivedRoyalTitleIn, 1988]
-
A.
nobleTitleAcquiredThrough
Indicates the manner, event, or process by which a person comes to obtain or be granted a particular noble title.
-
B.
royalTitleConfirmed
Indicates that an individual's royal title has been formally validated or officially recognized.
-
C.
usesRoyalTitle
Indicates that one entity refers to another using a royal title or honorific (such as king, queen, prince, or similar).
-
D.
honoraryTitleGrantedTo
Indicates that an honorary title has been formally conferred upon a particular entity.
-
E.
royalAppointment
chosen
Indicates a formal position, role, or honor that has been officially granted to an entity by a monarch or royal authority.
- F. None of above.
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_69d94e1888b48190bd750f839a26e99e |
completed | April 10, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69d94d354b488190adc83fb4f2770dd5 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.