Triple
T12576675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julie Schumann |
E300224
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Schumann |
E800323
|
NE 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: Schumann | Statement: [Julie Schumann, familyName, Schumann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schumann Context triple: [Julie Schumann, familyName, Schumann]
-
A.
Schumann
chosen
Schumann is a prominent German surname most famously associated with composer Robert Schumann and his pianist wife Clara Schumann.
-
B.
August Schumann
August Schumann was a German publisher and bookseller best known as the father of composer Robert Schumann and grandfather of pianist Marie Schumann.
-
C.
Emil Schumann
Emil Schumann was one of the children of the renowned German Romantic composer Robert Schumann and his pianist wife Clara Schumann.
-
D.
Ferdinand Schumann
Ferdinand Schumann was one of the sons of renowned German composer Robert Schumann and his wife, pianist Clara Schumann.
-
E.
Robert Schumann
Robert Schumann was a leading 19th-century German Romantic composer and influential music critic known for his expressive piano works, songs, and symphonic music.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954a73c148190bba8f16b1232fd46 |
completed | April 10, 2026, 7:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65597dc70819089ddc1794e9bd1b7 |
completed | May 2, 2026, 7:50 p.m. |
Created at: April 9, 2026, 4:51 p.m.