Triple
T10397385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senusret II |
E245054
|
entity |
| Predicate | coregencyClaim |
P93700
|
FINISHED |
| Object | possible short coregency with Amenemhat II |
—
|
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: possible short coregency with Amenemhat II | Statement: [Senusret II, coregencyClaim, possible short coregency with Amenemhat II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coregencyClaim Context triple: [Senusret II, coregencyClaim, possible short coregency with Amenemhat II]
-
A.
alsoClaimedBy
Indicates that the same item, statement, or resource is asserted or claimed by an additional party besides the primary one.
-
B.
relatedToClaimOf
Indicates a relationship where something is connected or pertinent to a specific claim or assertion.
-
C.
dissentClaimed
Indicates that an entity has expressed disagreement or opposition to a claim made by another entity.
-
D.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
E.
hasCollectiveRightClaim
Indicates that a group or collective entity asserts or holds a right or entitlement on behalf of its members.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9d0de448190b0bfd4d6c87d47fa |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e944fac4819093b0312aa0efd729 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:07 p.m.