Triple
T27847429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keys to the Heart |
E703860
|
entity |
| Predicate | youngerBrotherTalent |
P163735
|
FINISHED |
| Object | piano playing |
—
|
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: piano playing | Statement: [Keys to the Heart, youngerBrotherTalent, piano playing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: youngerBrotherTalent Context triple: [Keys to the Heart, youngerBrotherTalent, piano playing]
-
A.
youngerBrotherTrait
Indicates that one entity has the characteristic or role of being the younger brother in relation to another entity.
-
B.
youngerSonOf
Indicates that one person is the younger male child (son) of another person.
-
C.
youngerSibling
Indicates that one entity is the younger sibling of another in a family or sibling relationship.
-
D.
youngestBrotherRank
Indicates the ordinal position or rank of an entity among its youngest brothers within a family or sibling group.
-
E.
youngerBrotherRank
Indicates that one entity holds the position or status of a younger brother relative to another entity.
- F. None of above. chosen
Provenance (4 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63c045bd081908e0cb2a119202e8f |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63b3039808190b00bbd19161487f3 |
completed | May 2, 2026, 5:58 p.m. |
Created at: April 27, 2026, 6:08 p.m.