Triple
T34628935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | s-t-kꜣ |
E889217
|
entity |
| Predicate | associatedWithFather |
P63255
|
FINISHED |
| Object | Khufu |
E24430
|
NE 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: Khufu | Statement: [s-t-kꜣ, associatedWithFather, Khufu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFather Context triple: [s-t-kꜣ, associatedWithFather, Khufu]
-
A.
associatedWithPatriarch
Indicates that an entity has a relationship, connection, or affiliation with a patriarch, such as being under their authority, influence, or domain.
-
B.
relationshipWithFather
chosen
Indicates a familial relationship that specifically connects an individual to their father.
-
C.
associatedWithParents
Indicates a relationship where an entity is linked or connected to its parents in some relevant context.
-
D.
hasOwnerFatherOf
Indicates that the owner of an entity is the father of another specified entity.
-
E.
paternalRelativeOf
Indicates a family relationship where one person is a relative of another specifically through the father’s side of the family.
- F. None of above.
Provenance (4 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37412141348190b6743af6a78e880d |
completed | June 21, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:04 a.m.