Triple
T27436020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psusennes II |
E690784
|
entity |
| Predicate | spouseClaim |
P115011
|
FINISHED |
| Object | possibly Maatkare B |
—
|
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: possibly Maatkare B | Statement: [Psusennes II, spouseClaim, possibly Maatkare B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseClaim Context triple: [Psusennes II, spouseClaim, possibly Maatkare B]
-
A.
spouseClaimStatus
chosen
Indicates whether and how one person asserts or is recognized as being the spouse of another, such as claimed, unclaimed, or disputed marital status.
-
B.
spouseDivision
Indicates a division or separation between spouses, such as legal, physical, or relational separation within a marital relationship.
-
C.
spouseClaimReliability
Indicates how trustworthy or credible a claim made by a spouse is considered to be.
-
D.
spouseRecognition
Indicates that one entity formally acknowledges another entity as their spouse within a recognized relationship.
-
E.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
- 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 27, 2026, 12:43 p.m.