Triple
T267633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcussen & Søn pipe organ |
E5765
|
entity |
| Predicate | playedBy |
P9616
|
FINISHED |
| Object | organists |
—
|
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: organists | Statement: [Marcussen & Søn pipe organ, playedBy, organists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedBy Context triple: [Marcussen & Søn pipe organ, playedBy, organists]
-
A.
portrayedBy
Indicates that one entity serves as the actor or performer who represents or plays the role of another entity in a work or medium.
-
B.
playedRoleIn
Indicates that an entity performed or assumed a specific role or character within a particular event, production, or context.
-
C.
spokenBy
Indicates that a particular utterance, statement, or piece of speech is produced or said by a specific entity.
-
D.
starredActor
Indicates that an actor performed a leading or significant role in a particular production or work.
-
E.
notableCastMember
Indicates that an entity is a member of the cast of another entity (such as a film, show, or production) and is considered particularly notable or significant in that role.
- F. None of above. chosen
Provenance (4 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25dacf60c8190a5c3ef455b9a8b20 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b70d99c819085d8381a313a2a34 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25d6ec9688190b2ba027756b57d25 |
completed | Feb. 28, 2026, 3:13 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.