Triple
T34048233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herakleopolitan Egypt |
E873144
|
entity |
| Predicate | hasDynastyCenter |
P123151
|
FINISHED |
| Object | Herakleopolis Magna |
—
|
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: Herakleopolis Magna | Statement: [Herakleopolitan Egypt, hasDynastyCenter, Herakleopolis Magna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDynastyCenter Context triple: [Herakleopolitan Egypt, hasDynastyCenter, Herakleopolis Magna]
-
A.
importantDynastyCenterFor
Indicates that a location served as a significant political, cultural, or administrative center for a particular dynasty.
-
B.
hasCurrentDynasty
Indicates that an entity is currently ruled, governed, or controlled by the specified dynasty.
-
C.
administrativeCenterForEmpire
Indicates that a location served as the main administrative center or capital for a particular empire.
-
D.
associatedDynastyCapital
chosen
Indicates a relationship where a dynasty is linked to the city that served as its capital.
-
E.
isDiplomaticCenterOf
Indicates that a location serves as the primary site or hub for conducting diplomatic activities and relations for a specified entity.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.