Triple
T30943578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BB-28 |
E788324
|
entity |
| Predicate | emotionallyLinkedTo |
P23414
|
FINISHED |
| Object | Sam Porter Bridges |
—
|
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: Sam Porter Bridges | Statement: [BB-28, emotionallyLinkedTo, Sam Porter Bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emotionallyLinkedTo Context triple: [BB-28, emotionallyLinkedTo, Sam Porter Bridges]
-
A.
emotionallyAttachedTo
chosen
Indicates that one entity has a strong emotional bond, affection, or dependence directed toward another entity.
-
B.
emotionalFocusOf
Indicates that one entity is the primary target or center of another entity’s emotions or emotional attention.
-
C.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
D.
relationshipImpact
Indicates how one entity’s relationship with another affects or changes those entities or their interaction.
-
E.
relationshipToHeed
Indicates a relationship in which one entity is expected to pay attention to, respect, or follow the guidance, warnings, or wishes of 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:53 p.m.