Triple
T26472223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | محافظة الدقهلية |
E665932
|
entity |
| Predicate | عاصمة_المحافظة |
P110991
|
FINISHED |
| Object | مدينة المنصورة |
—
|
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: مدينة المنصورة | Statement: [محافظة الدقهلية, عاصمة_المحافظة, مدينة المنصورة]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: عاصمة_المحافظة Context triple: [محافظة الدقهلية, عاصمة_المحافظة, مدينة المنصورة]
-
A.
isDistrictCapitalOf
Indicates that a location serves as the administrative or governmental capital of a specified district.
-
B.
capitalCityGoverned
Indicates that a particular capital city is under the administrative or political authority of a specified governing body or jurisdiction.
-
C.
capitalAreaOf
Indicates that a specified area value represents the total land or geographic size of the capital city of a given entity.
-
D.
cityAsSeatOfGovernment
Indicates that a city serves as the official seat or location of a government’s central authority or administration.
-
E.
provinceHeadquarters
chosen
Indicates that one entity serves as the main administrative or organizational headquarters for a province associated with the other 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612c8eb1881909aa03c234e3abcb4 |
completed | May 2, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:20 a.m.