Triple
T19433368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amenmesse |
E486169
|
entity |
| Predicate | hasDisputedLegitimacy |
P135868
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Amenmesse, hasDisputedLegitimacy, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisputedLegitimacy Context triple: [Amenmesse, hasDisputedLegitimacy, true]
-
A.
legalStatusDebatedBy
Indicates that the legal status of an entity is the subject of dispute, discussion, or controversy among parties or authorities.
-
B.
hasDisputedCircumscription
Indicates that there is disagreement or uncertainty about how the boundaries or scope of something are formally defined or delimited.
-
C.
hasDisputedAttribution
Indicates that the attribution of an entity (such as its creator, source, or origin) is contested or not universally agreed upon.
-
D.
hasDisputedSector
Indicates that there exists a sector or area whose ownership, control, or status between the related entities is contested or not mutually agreed upon.
-
E.
capitalContested
Indicates that the status of being the capital of a region or country is disputed or claimed by multiple parties.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6335dae10819096e1825741f814ed |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.