Triple
T6439512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ein deutsches Requiem |
E138181
|
entity |
| Predicate | opusListPosition |
P19302
|
FINISHED |
| Object | major early large-scale work by Brahms |
—
|
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: major early large-scale work by Brahms | Statement: [Ein deutsches Requiem, opusListPosition, major early large-scale work by Brahms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opusListPosition Context triple: [Ein deutsches Requiem, opusListPosition, major early large-scale work by Brahms]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
hasPositionInBook
Indicates that an entity occupies a specific position or location within a book.
-
C.
positionInAuthorOeuvre
chosen
Indicates the relative placement or order of a work within an author's overall body of work.
-
D.
positionSought
Indicates the specific role, job, or position that an entity is aiming to obtain or apply for.
-
E.
positionNumber
Indicates the specific ordinal or identifying number assigned to a position within an ordered set or organizational structure.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06967241c8190965bac395adf2d03 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:45 p.m.