Triple
T33354878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobby Brahms |
E854041
|
entity |
| Predicate | hasThemeInvolving |
P76865
|
FINISHED |
| Object | friendship |
—
|
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: friendship | Statement: [Bobby Brahms, hasThemeInvolving, friendship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThemeInvolving Context triple: [Bobby Brahms, hasThemeInvolving, friendship]
-
A.
hasThemeInStory
chosen
Indicates that a particular theme is present or plays a significant role within a given story.
-
B.
followsInTheme
Indicates that one element continues or succeeds another while maintaining the same theme or thematic context.
-
C.
hasThemeRelationship
Indicates a relationship where one entity is thematically related to, or centered around, another entity as its main subject or topic.
-
D.
hasBeenInvolvedIn
Indicates that an entity has participated in, taken part in, or been connected to a particular event, activity, or situation.
-
E.
hadThemeElement
Indicates that an entity includes, involves, or is characterized by a specific thematic element as part of its overall theme.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 1:34 a.m.