Triple
T23762151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sean Saves the World |
E587277
|
entity |
| Predicate | protagonistFamilyRole |
P80421
|
FINISHED |
| Object | single father |
—
|
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: single father | Statement: [Sean Saves the World, protagonistFamilyRole, single father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistFamilyRole Context triple: [Sean Saves the World, protagonistFamilyRole, single father]
-
A.
protagonistFamilyStatus
chosen
Indicates the familial role or position that a character holds in relation to the story’s protagonist.
-
B.
protagonistFamilyName
Indicates that the subject is the family name (surname) of the story’s protagonist.
-
C.
hasProtagonistFamilyMember
Indicates that a work’s protagonist has a specified individual as a member of their family.
-
D.
protagonistFamilyOrigin
Indicates that a character’s family background, ancestry, or place of origin is associated with the story’s protagonist.
-
E.
protagonistFather
Indicates that one entity is the father of the story’s protagonist.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdb34d5c81909087385066a52e61 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:14 p.m.