Triple
T8859815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emil Schumann |
E210857
|
entity |
| Predicate | hasMotherNotableRole |
P50640
|
FINISHED |
| Object | concert pianist |
—
|
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: concert pianist | Statement: [Emil Schumann, hasMotherNotableRole, concert pianist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMotherNotableRole Context triple: [Emil Schumann, hasMotherNotableRole, concert pianist]
-
A.
motherNotableFor
chosen
Indicates that an individual’s mother is recognized or distinguished for a particular achievement, role, or characteristic.
-
B.
motherNotableAsMemberOf
Indicates that the subject’s mother is particularly recognized or notable for being a member of the specified group, organization, or entity.
-
C.
isMotherOf
Indicates that one entity is the female parent who has given birth to or legally/ socially parents the other entity.
-
D.
notableHolderMother
Indicates that the mother of an entity is a notable or distinguished holder of a particular role, title, or attribute associated with that entity.
-
E.
hasFamousNamesakeRole
Indicates that an entity has a role or position that shares its name with a well-known or historically notable person.
- 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e712d08190bfb1c4ba3acaea90 |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:50 p.m.