Triple
T842318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minya |
E18203
|
entity |
| Predicate | isRegionalCenterOf |
P1474
|
FINISHED |
| Object | administration |
—
|
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: administration | Statement: [Minya, isRegionalCenterOf, administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalCenterOf Context triple: [Minya, isRegionalCenterOf, administration]
-
A.
isMajorCenterOf
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
B.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
C.
isNationalAdministrativeCenter
Indicates that a location serves as the primary administrative or governmental center for a nation.
-
D.
hasAdministrativeCenter
chosen
Indicates that an administrative unit (such as a region, district, or municipality) has a specific place designated as its main governing or administrative center.
-
E.
hasPopulationCenterType
Indicates the classification of a population center by its type, such as city, town, village, or other settlement category.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abe8a0bc81909b54af465e67be1f |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7f396c8190aa8b8dfbe0b4f732 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.