Triple
T16779472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michal |
E407818
|
entity |
| Predicate | emotionalBond |
P23414
|
FINISHED |
| Object | strong attachment to Katurian |
—
|
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: strong attachment to Katurian | Statement: [Michal, emotionalBond, strong attachment to Katurian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emotionalBond Context triple: [Michal, emotionalBond, strong attachment to Katurian]
-
A.
emotionallyAttachedTo
chosen
Indicates that one entity has a strong emotional bond, affection, or dependence directed toward another entity.
-
B.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
C.
emotionalDynamic
Indicates how emotions, moods, or affective states change, interact, or influence each other between entities over time.
-
D.
emotionalCounterpartOf
Indicates that one entity serves as the emotional equivalent, complement, or matching emotional role of another entity.
-
E.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21401b881909bbbc7382e851a90 |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.