Triple
T24235562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander of Gilead |
E601869
|
entity |
| Predicate | hasConcubineType |
P155293
|
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: [Commander of Gilead, hasConcubineType, Handmaid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConcubineType Context triple: [Commander of Gilead, hasConcubineType, Handmaid]
-
A.
hasConcubineFrom
Indicates that a person has a concubine whose origin or affiliation is from a specified place or source.
-
B.
concubineOf
Indicates a relationship where one person is a concubine belonging to or maintained by another person.
-
C.
hasSecretMarriageWith
Indicates a relationship where two entities are secretly married to each other, with the marriage intentionally concealed from others.
-
D.
hasAffairWith
Indicates that one entity is engaged in a secret or illicit romantic or sexual relationship with another entity, typically outside a committed partnership.
-
E.
hasAnotherWife
Indicates that a person is married to more than one wife, specifying the existence of an additional wife beyond the first.
- F. None of above. chosen
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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f28a9b52708190b319a9e502a61d13 |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:02 a.m.