Triple
T34477415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mersekhemre Ined |
E885076
|
entity |
| Predicate | capitalLikelyAt |
P149844
|
FINISHED |
| Object | Itjtawy |
—
|
NE NERFINISHED |
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 | Statement: [Mersekhemre Ined, capitalLikelyAt, Itjtawy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalLikelyAt Context triple: [Mersekhemre Ined, capitalLikelyAt, Itjtawy]
-
A.
capitalPossiblyAt
chosen
Indicates a possible or uncertain capital relationship, where one location may be the capital of another but this is not definitively established.
-
B.
capitalApproximateLocation
Indicates that the relationship specifies an approximate or general geographic location of a capital city rather than its precise coordinates.
-
C.
capitalSince
Indicates that an entity has served as the capital of another entity starting from a specified point in time.
-
D.
capital
Indicates that one place serves as the official seat of government or primary administrative center for another political entity.
-
E.
capitalLaterAt
Indicates that one entity becomes the capital of another entity at a later point in time than a referenced capital or event.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 1, 2026, 2:01 a.m.