Triple
T5049218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Philharmonic Orchestra |
E113742
|
entity |
| Predicate | hasPatronType |
P37185
|
FINISHED |
| Object | royal patronage |
—
|
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: royal patronage | Statement: [Royal Philharmonic Orchestra, hasPatronType, royal patronage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatronType Context triple: [Royal Philharmonic Orchestra, hasPatronType, royal patronage]
-
A.
patronType
chosen
Indicates the classification or category of a patron in relation to a service, institution, or resource.
-
B.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
C.
hasRateType
Indicates the specific category or scheme under which a rate (such as a price, fee, or interest) is defined or applied.
-
D.
hasReservationType
Indicates that an entity is associated with a specific category or type of reservation.
-
E.
hasNotablePatron
Indicates that an entity is significantly supported, sponsored, or championed by a distinguished or influential patron.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.