Triple
T4861272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Offred |
E108664
|
entity |
| Predicate | roleInGilead |
P3707
|
FINISHED |
| Object | Handmaid |
—
|
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: Handmaid | Statement: [Offred, roleInGilead, Handmaid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInGilead Context triple: [Offred, roleInGilead, Handmaid]
-
A.
prisonRole
Indicates a role or function that an entity holds within the context or system of a prison.
-
B.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
C.
deFactoRole
chosen
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
D.
designedRole
Indicates that one entity has been created, configured, or intended to serve a particular function, purpose, or role in relation to another entity.
-
E.
roleInDialogue
Indicates that an entity participates in a dialogue with a specific conversational role (e.g., speaker, listener, moderator) relative to other participants.
- 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_69bd440b965081908b0557721cae6338 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d5e247c8190b6ae4e9b529f0345 |
completed | March 20, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69bd6c27334481909ba8ac80854f7d8e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.