Triple
T24317678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Philharmonic Society |
E612866
|
entity |
| Predicate | honoraryMembershipFor |
P49169
|
FINISHED |
| Object | distinguished musicians |
—
|
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: distinguished musicians | Statement: [Royal Philharmonic Society, honoraryMembershipFor, distinguished musicians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoraryMembershipFor Context triple: [Royal Philharmonic Society, honoraryMembershipFor, distinguished musicians]
-
A.
hasHonoraryMember
chosen
Indicates that an entity is recognized as an honorary (non-regular) member of another entity, typically without full rights or obligations of standard membership.
-
B.
honoraryAwardsEligibleFor
Indicates that an entity qualifies to receive one or more honorary awards.
-
C.
includesHonoraryAwardsFor
Indicates that one entity contains or lists honorary awards that have been granted to another entity.
-
D.
honoraryAwardsPossible
Indicates that it is possible for honorary awards to be granted or conferred in the given context.
-
E.
confersHonorificStatus
Indicates that one entity formally grants an honorific title, rank, or status to another entity.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292a916c8819096d018e7ffaf483b |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:47 a.m.