Triple
T1901491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Walton |
E37697
|
entity |
| Predicate | wroteForEnsemble |
P2831
|
FINISHED |
| Object | chorus and orchestra |
—
|
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: chorus and orchestra | Statement: [William Walton, wroteForEnsemble, chorus and orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteForEnsemble Context triple: [William Walton, wroteForEnsemble, chorus and orchestra]
-
A.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
-
B.
intendedEnsemble
Indicates that one entity is designed, chosen, or specified to function as the ensemble or group counterpart associated with another entity.
-
C.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
D.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
E.
wrote
chosen
Indicates that an entity is the author or creator of a written work involving another entity.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafe9f8b0819086d8f6288511c66d |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.