Triple
T36860683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nerikare |
E910925
|
entity |
| Predicate | capitalRegionHypothesis |
P195749
|
FINISHED |
| Object | Itjtawy vicinity |
—
|
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: Itjtawy vicinity | Statement: [Nerikare, capitalRegionHypothesis, Itjtawy vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalRegionHypothesis Context triple: [Nerikare, capitalRegionHypothesis, Itjtawy vicinity]
-
A.
capitalRegionIncluded
Indicates that a specified region contains or encompasses the capital area of a given political or administrative entity.
-
B.
traditionalCapitalRegionOf
Indicates that a region is recognized as the traditional or historical capital area of a specified larger territory or entity.
-
C.
capitalRegionOf
Indicates that one region serves as the capital or primary administrative center of another region.
-
D.
hitCapitalRegion
Indicates that an action, event, or impact has struck or affected the capital region of a specified area or jurisdiction.
-
E.
capitalRegionDesignated
Indicates that a specific region has been officially designated as the capital area for a given political or administrative entity.
- 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: May 3, 2026, 4:13 p.m.