Triple
T27878304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ben Wrightman |
E705012
|
entity |
| Predicate | relationshipComplicationCause |
P47731
|
FINISHED |
| Object | devotion to Boston Red Sox |
—
|
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: devotion to Boston Red Sox | Statement: [Ben Wrightman, relationshipComplicationCause, devotion to Boston Red Sox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipComplicationCause Context triple: [Ben Wrightman, relationshipComplicationCause, devotion to Boston Red Sox]
-
A.
hasComplicatedRelationshipWith
chosen
Indicates that one entity is involved in a complex, often ambiguous or difficult-to-define interpersonal or relational dynamic with another entity.
-
B.
relationshipContext
Indicates the situational or social setting in which a relationship between entities exists or occurs.
-
C.
relationshipFocus
Indicates a relationship where particular attention, priority, or emphasis is placed on the connection between two or more entities.
-
D.
reportsRelationship
Indicates that one entity formally provides information, findings, or status about another entity or situation.
-
E.
haveRelationshipWith
Indicates that one entity is in some form of defined relationship or association 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
Created at: April 27, 2026, 6:28 p.m.