Triple
T29026191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scenes from Childhood |
E737598
|
entity |
| Predicate | mostFamousPiece |
P114678
|
FINISHED |
| Object | Träumerei |
—
|
NE NERFINISHED |
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: Träumerei | Statement: [Scenes from Childhood, mostFamousPiece, Träumerei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostFamousPiece Context triple: [Scenes from Childhood, mostFamousPiece, Träumerei]
-
A.
mostFamousPlay
Indicates that the related entity is the play for which a person is best or most widely known.
-
B.
mostFamouslyRecordedBy
Indicates that an item (such as a work, song, or performance) is best known or most widely associated with having been recorded by a particular entity.
-
C.
mostFamousBearer
Indicates that one entity is the most widely recognized or renowned individual associated with a particular name, title, or attribute compared to all other bearers of it.
-
D.
notableFeatureOfWork
Indicates that a particular feature, characteristic, or aspect is a notable or distinguishing element of a given work.
-
E.
isOneOfMostSuccessfulWorksOf
chosen
Indicates that one entity is among the most successful works or creations associated with 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66009953c8190869c9093c304a198 |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:52 a.m.