Triple
T37896164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie Simms |
E945285
|
entity |
| Predicate | primaryProtagonistIn |
P9202
|
FINISHED |
| Object | Scent of a Woman |
E278936
|
NE 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: Scent of a Woman | Statement: [Charlie Simms, primaryProtagonistIn, Scent of a Woman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryProtagonistIn Context triple: [Charlie Simms, primaryProtagonistIn, Scent of a Woman]
-
A.
mainProtagonist
chosen
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
B.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
C.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
D.
hasMainProtagonistTrait
Indicates that the specified trait is a defining or primary characteristic of the main protagonist.
-
E.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
- F. None of above.
Provenance (4 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d1c9f748190a87010559e1c7ad4 |
completed | June 28, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.