Triple
T31173303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary |
E794671
|
entity |
| Predicate | relationToTitle |
P34778
|
FINISHED |
| Object | one of the wives of the dead |
—
|
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: one of the wives of the dead | Statement: [Mary, relationToTitle, one of the wives of the dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToTitle Context triple: [Mary, relationToTitle, one of the wives of the dead]
-
A.
titleRelation
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
-
B.
termRelationTo
chosen
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
C.
relatedTitleHolder
Indicates that one entity holds a title or position that is related or connected to the title or position held by another entity.
-
D.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
E.
titleHolderRelation
Indicates that one entity holds, possesses, or is designated as the bearer of a specific title associated with another entity.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:07 p.m.