Triple
T20034748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal College of Organists |
E497223
|
entity |
| Predicate | focusInstrument |
P17140
|
FINISHED |
| Object | pipe organ |
—
|
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: pipe organ | Statement: [Royal College of Organists, focusInstrument, pipe organ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusInstrument Context triple: [Royal College of Organists, focusInstrument, pipe organ]
-
A.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
B.
primaryInstrumentalFocus
chosen
Indicates that one entity serves as the main or most emphasized instrument or means by which another entity performs an action or achieves an effect.
-
C.
focusShift
Indicates a change in attention or emphasis from one entity or topic to another.
-
D.
focusFeature
Indicates that one entity is the primary or emphasized feature, aspect, or attribute being highlighted or concentrated on in relation to another.
-
E.
focusOf
Indicates that one entity is the primary subject, target, or center of attention, activity, or interest for 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662e76f8481909c006921cbbfd060 |
completed | April 20, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:36 p.m.