Triple
T32897362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ride of the Valkyries |
E841511
|
entity |
| Predicate | belongsToWorkNumber |
P171929
|
FINISHED |
| Object | WWV 86 |
—
|
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: WWV 86 | Statement: [Ride of the Valkyries, belongsToWorkNumber, WWV 86]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToWorkNumber Context triple: [Ride of the Valkyries, belongsToWorkNumber, WWV 86]
-
A.
appearsInWorkNumber
Indicates that an entity is featured or occurs within a specific numbered work in a series or collection.
-
B.
belongsToWorkBy
Indicates that something is part of, or associated with, a work that was created by a specific agent or creator.
-
C.
workNumberInKey
chosen
Indicates that a specific work or item is identified or referenced by a particular number used as a key in some cataloging or indexing system.
-
D.
hasNumberWithinWork
Indicates that a specific number or numeric value is contained, referenced, or used within a particular work (such as a document, publication, or creative piece).
-
E.
associatedKeyWorkNumbering
Indicates that a key work is linked to, or identified by, a specific numbering system or reference number.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: May 1, 2026, 1:18 a.m.