Triple
T4253294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luxor Governorate |
E95909
|
entity |
| Predicate | governorateCode |
P20781
|
FINISHED |
| Object | EG-LX |
—
|
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: EG-LX | Statement: [Luxor Governorate, governorateCode, EG-LX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governorateCode Context triple: [Luxor Governorate, governorateCode, EG-LX]
-
A.
governorateOrDistrict
Indicates that one administrative region is a governorate or district that encompasses, governs, or is otherwise the primary subnational division for another area or locality.
-
B.
governorateOf
Indicates that one entity is the governorate (administrative region) to which another entity belongs or is located within.
-
C.
governorateType
Indicates the specific classification or category of a governorate within an administrative or governmental hierarchy.
-
D.
stateSubdivisionCode
chosen
Indicates the standardized code that identifies a specific subdivision (such as a state, province, or region) within a larger country or territory.
-
E.
districtCode
Indicates that an entity is associated with, or identified by, a specific administrative district code.
- 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ebe6fbc8190a89269b478b3f435 |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.