Triple
T12808518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantata III (Christmas Oratorio) |
E306206
|
entity |
| Predicate | hasWorkOrderWithinOratorio |
P106062
|
FINISHED |
| Object | Part III |
—
|
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: Part III | Statement: [Cantata III (Christmas Oratorio), hasWorkOrderWithinOratorio, Part III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkOrderWithinOratorio Context triple: [Cantata III (Christmas Oratorio), hasWorkOrderWithinOratorio, Part III]
-
A.
workNumberWithinOratorio
chosen
Indicates that a specific work is identified by its numerical position within an oratorio.
-
B.
hasOrchestration
Indicates that one entity coordinates, manages, or sequences the actions or interactions of another entity or set of entities.
-
C.
hasOrchestrationBy
Indicates that something is organized, coordinated, or arranged by a specified agent or entity.
-
D.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
E.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e808130819080f404b3a7462c2e |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.