Triple
T24209592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semerkhet |
E600493
|
entity |
| Predicate | spouseHypothesis |
P114351
|
FINISHED |
| Object | Betrest |
—
|
NE NERFINISHED |
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: Betrest | Statement: [Semerkhet, spouseHypothesis, Betrest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseHypothesis Context triple: [Semerkhet, spouseHypothesis, Betrest]
-
A.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
B.
possiblySpouse
chosen
Indicates that two entities may be spouses, reflecting an uncertain or hypothesized marital relationship between them.
-
C.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of another entity.
-
D.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
-
E.
spouseInFamily
Indicates that a person is a spouse (married partner) within the context of a specific family unit.
- 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_69e2953344c48190875730c7d52112a0 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f282020a5881909df47f766c3ee7af |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:53 p.m.