Triple
T1102845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narmer |
E25418
|
entity |
| Predicate | disputedIssues |
P1783
|
FINISHED |
| Object | identity with Menes |
—
|
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: identity with Menes | Statement: [Narmer, disputedIssues, identity with Menes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputedIssues Context triple: [Narmer, disputedIssues, identity with Menes]
-
A.
disputedSections
Indicates that specific parts or portions of something are contested, challenged, or not mutually agreed upon between parties.
-
B.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
C.
disputedAspect
Indicates that a particular feature, detail, or component of something is subject to disagreement or contention between parties.
-
D.
statusDisputedBy
Indicates that the validity, accuracy, or recognition of a status is being challenged or contested by a specified party.
-
E.
controversy
chosen
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
- F. None of above.
Provenance (3 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9c375848190baec4d534f489616 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b7472c848190b0643872f67084a2 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.