Triple
T33966346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flora McGrath |
E870863
|
entity |
| Predicate | hasStrongEmotionalBondWith |
P23414
|
FINISHED |
| Object | piano |
—
|
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 | Statement: [Flora McGrath, hasStrongEmotionalBondWith, piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrongEmotionalBondWith Context triple: [Flora McGrath, hasStrongEmotionalBondWith, piano]
-
A.
emotionallyAttachedTo
chosen
Indicates that one entity has a strong emotional bond, affection, or dependence directed toward another entity.
-
B.
emotionalRelationshipTo
Indicates an emotional connection or attitude that one entity feels toward another, such as affection, dislike, attachment, or other emotional states.
-
C.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
D.
haveRelationshipWith
Indicates that one entity is in some form of defined relationship or association with another entity.
-
E.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:50 a.m.