Triple
T18537904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khaba |
E453013
|
entity |
| Predicate | possiblyIdenticalWith |
P132057
|
FINISHED |
| Object | Huni (hypothesis) |
—
|
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: Huni (hypothesis) | Statement: [Khaba, possiblyIdenticalWith, Huni (hypothesis)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possiblyIdenticalWith Context triple: [Khaba, possiblyIdenticalWith, Huni (hypothesis)]
-
A.
isRedundantWith
Indicates that one entity duplicates or overlaps the function, information, or effect of another such that one could be removed without significant loss.
-
B.
identifiedAsSameObjectAs
Indicates that two referenced entities are recognized or treated as being the very same underlying object or instance.
-
C.
sameMatchAs
Indicates that two entities are considered equivalent or represent the same underlying match or correspondence in a given context.
-
D.
hasEquivalent
Indicates that two entities are considered equal in value, meaning, or function within a given context.
-
E.
mayDifferFrom
Indicates that one entity is allowed or expected to be different from another entity, without requiring them to be identical.
- F. None of above. chosen
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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534030bd88190b25b95305a12a0c1 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:37 a.m.