Triple
T22505664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HWV 348 |
E556381
|
entity |
| Predicate | hasWorkNumberInSet |
P57122
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [HWV 348, hasWorkNumberInSet, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkNumberInSet Context triple: [HWV 348, hasWorkNumberInSet, 1]
-
A.
workNumberInSet
chosen
Indicates that a particular work number belongs to, or is included within, a specified set of work numbers.
-
B.
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).
-
C.
hasWorkCount
Indicates the number of works (such as items, creations, or outputs) associated with a given entity.
-
D.
hasWorkAsSetting
Indicates that a particular work (such as a story, film, or artwork) takes place in or uses a specified location, time, or environment as its setting.
-
E.
hasWorkInCollection
Indicates that a work or item is included as part of a particular collection.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5bf0f0819093426d83ebd80ef0 |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.