Triple
T32147931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burna-Buriash II |
E821070
|
entity |
| Predicate | claimedEqualityWith |
P182270
|
FINISHED |
| Object | pharaoh of Egypt |
—
|
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: pharaoh of Egypt | Statement: [Burna-Buriash II, claimedEqualityWith, pharaoh of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedEqualityWith Context triple: [Burna-Buriash II, claimedEqualityWith, pharaoh of Egypt]
-
A.
equalityCase
Indicates that two entities are considered equal or equivalent under a specific case or case-sensitivity condition.
-
B.
requiresEqualTreatmentWith
Indicates that one entity must be treated in the same way and to the same extent as another entity, without preferential or discriminatory differences.
-
C.
claimedRight
Indicates that an entity asserts or demands a right or entitlement in relation to another entity or resource.
-
D.
claimedSee
Indicates that one entity asserted or reported having seen or visually perceived another entity or event.
-
E.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: May 1, 2026, 12:31 a.m.