Triple
T23877293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | II: Expectans expectavi Dominum |
E592902
|
entity |
| Predicate | usesChoir |
P4009
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [II: Expectans expectavi Dominum, usesChoir, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesChoir Context triple: [II: Expectans expectavi Dominum, usesChoir, yes]
-
A.
hasChoir
chosen
Indicates that an entity possesses, maintains, or is associated with a choir.
-
B.
usesChorale
Indicates that one entity incorporates or employs a chorale (a hymn-like musical piece) within its structure or content.
-
C.
hasChoristersSingAt
Indicates that choristers perform singing at a specified event, location, or occasion.
-
D.
usesChorusBetweenStanzas
Indicates that a recurring chorus section is inserted between successive stanzas of a piece (such as a song or poem).
-
E.
hasChorusIn
Indicates that a musical work includes a chorus section within the specified part or segment.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cc02277c8190b0c15d6525f3b38d |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:15 p.m.