Triple
T32823248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of Egypt |
E839487
|
entity |
| Predicate | maritalRelationToPharaoh |
P97855
|
FINISHED |
| Object | wife |
—
|
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: wife | Statement: [Queen of Egypt, maritalRelationToPharaoh, wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalRelationToPharaoh Context triple: [Queen of Egypt, maritalRelationToPharaoh, wife]
-
A.
marriedToPharaoh
chosen
Indicates that one entity is the spouse of a pharaoh in a marital relationship.
-
B.
associatedWithPharaoh
Indicates a relationship in which an entity has a connection, link, or involvement with a pharaoh, such as through service, rule, influence, or historical association.
-
C.
motherOfPharaoh
Indicates that one entity is the mother (biological or adoptive) of another entity who holds the title or role of pharaoh.
-
D.
familyRelationToEmperor
Indicates that one entity is related to an emperor by family ties, specifying a kinship or familial connection between them.
-
E.
maritalRelations
Indicates a legally or socially recognized spousal relationship or marriage-based connection between two entities.
- 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_69f3493df9008190a8f5d843dcd77704 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:15 a.m.