Triple
T29348040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilukhepa |
E744223
|
entity |
| Predicate | spouseNameAndTitle |
P156461
|
FINISHED |
| Object | Amenhotep III, pharaoh of the 18th Dynasty |
—
|
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: Amenhotep III, pharaoh of the 18th Dynasty | Statement: [Gilukhepa, spouseNameAndTitle, Amenhotep III, pharaoh of the 18th Dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseNameAndTitle Context triple: [Gilukhepa, spouseNameAndTitle, Amenhotep III, pharaoh of the 18th Dynasty]
-
A.
spouseNameWithTitle
chosen
Indicates that a person’s spouse is identified by name together with an associated honorific or title.
-
B.
hasSpouseTitle
Indicates that a person’s spouse holds a particular title or honorific designation.
-
C.
isSpouseOfTitle
Indicates that one entity holds a spousal relationship specifically associated with a titled or honorific status of another entity.
-
D.
currentTitleHolderSpouseOf
Indicates that one entity is the current spouse of the individual who presently holds a specified title.
-
E.
spouse name
Indicates that one entity is the legally recognized husband or wife of the other, specifying the partner’s name in a marital relationship.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 28, 2026, 2:03 p.m.