Triple
T30649931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ombline |
E780225
|
entity |
| Predicate | mainCharacterOccupationOrRole |
P21567
|
FINISHED |
| Object | young mother |
—
|
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: young mother | Statement: [Ombline, mainCharacterOccupationOrRole, young mother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharacterOccupationOrRole Context triple: [Ombline, mainCharacterOccupationOrRole, young mother]
-
A.
featuresProtagonistOccupation
chosen
Indicates that the work’s main character has a specified occupation or job role.
-
B.
roleOfCharacter
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
-
C.
otherProtagonistOccupation
Indicates that another main character in the narrative has a specific occupation or job role.
-
D.
protagonistParentOccupation
Indicates the occupation or job held by the protagonist’s parent in the described context.
-
E.
roleForProtagonist
Indicates the specific narrative or functional role that an entity plays in relation to the story’s main 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 29, 2026, 8:30 p.m.