Triple
T3289314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul D |
E69061
|
entity |
| Predicate | hasBackstoryEvent |
P22468
|
FINISHED |
| Object | separation from the other Sweet Home men |
—
|
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: separation from the other Sweet Home men | Statement: [Paul D, hasBackstoryEvent, separation from the other Sweet Home men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBackstoryEvent Context triple: [Paul D, hasBackstoryEvent, separation from the other Sweet Home men]
-
A.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
B.
hasTragicPast
Indicates that an entity has experienced a significantly sorrowful or traumatic history that influences its present state or characterization.
-
C.
hadEvent
chosen
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
-
D.
hasOriginStoryLocation
Indicates that an entity’s origin story takes place at or is associated with a specific location.
-
E.
hasAllyInStory
Indicates that one entity is portrayed as an ally or supportive partner of another entity within the context of a specific story or narrative.
- 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_69ad859d45748190b0742408c954b39f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb05a3e5c819082552a7a911e3230 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.