Triple
T36620955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiaʼa |
E904034
|
entity |
| Predicate | hasPharaohHusband |
P97855
|
FINISHED |
| Object | Amenhotep II |
—
|
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 II | Statement: [Tiaʼa, hasPharaohHusband, Amenhotep II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPharaohHusband Context triple: [Tiaʼa, hasPharaohHusband, Amenhotep II]
-
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.
majorPharaoh
Indicates that the subject is recognized as a principal or highly significant pharaoh in relation to the object (such as a period, dynasty, or context).
-
E.
lastPharaoh
Indicates that the subject is the final individual to have held the position or role of pharaoh in a given context.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:11 p.m.