Triple
T25243861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Songs of Farewell |
E632543
|
entity |
| Predicate | sixthMovementTextIncipit |
P158066
|
FINISHED |
| Object | Lord, let me know mine end |
—
|
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: Lord, let me know mine end | Statement: [Songs of Farewell, sixthMovementTextIncipit, Lord, let me know mine end]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sixthMovementTextIncipit Context triple: [Songs of Farewell, sixthMovementTextIncipit, Lord, let me know mine end]
-
A.
fourthMovementTextSource
Indicates that a source provides the textual material used in the fourth movement of a work.
-
B.
firstMovement
Indicates that an entity represents the initial or earliest movement, action, or motion in a sequence of movements.
-
C.
fifthMovement
Indicates that one entity is the fifth movement or section in a sequence of movements within a larger structured work or process.
-
D.
sixthTrack
Indicates that one entity is the sixth track in an ordered sequence or collection of tracks associated with another entity.
-
E.
fourthMovementTitle
Indicates the title or name given to the fourth movement of a multi-movement musical work.
- 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f480854fb081909304508dfab21164 |
completed | May 1, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 1:10 p.m.