Triple
T29854188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benedictus qui venit |
E758141
|
entity |
| Predicate | firstComposerOfSetting |
P142361
|
FINISHED |
| Object | Franz Schubert |
—
|
NE NERFINISHED |
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: Franz Schubert | Statement: [Benedictus qui venit, firstComposerOfSetting, Franz Schubert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstComposerOfSetting Context triple: [Benedictus qui venit, firstComposerOfSetting, Franz Schubert]
-
A.
firstComposed
chosen
Indicates that one entity is the earliest or original work that a creator composed before any subsequent compositions.
-
B.
setComposer
Indicates that an entity assigns or specifies another entity as the composer of a work or item.
-
C.
possibleComposer
Indicates that an entity is a candidate or hypothesized creator/composer of another entity, without asserting this authorship as certain.
-
D.
dedicatedComposer
Indicates that one entity is a composer who is devoted or committed specifically to another entity or purpose.
-
E.
creatorRoleOfComposer
Indicates that an entity serves in the role of composer as the creator of 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a0143a4ab3c8190a240b0facfe130a9 |
completed | May 11, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_6a01426b2d4481908654bfa4a02c457d |
completed | May 11, 2026, 2:43 a.m. |
Created at: April 29, 2026, 5:45 p.m.