Triple
T4253292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luxor Governorate |
E95909
|
entity |
| Predicate | establishedAsGovernorate |
P42468
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Luxor Governorate, establishedAsGovernorate, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsGovernorate Context triple: [Luxor Governorate, establishedAsGovernorate, 2009]
-
A.
governorateEstablished
chosen
Indicates that a particular governorate (administrative region) was formally created or brought into official existence at a certain time or by a specific act.
-
B.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
-
C.
governorateOf
Indicates that one entity is the governorate (administrative region) to which another entity belongs or is located within.
-
D.
establishedAsAutonomousRegion
Indicates that an area has been formally designated and recognized as an autonomous region with a degree of self-governance.
-
E.
governorateCapitalStatusSince
Indicates the point in time since which a particular place has held the status of being the capital of a governorate.
- 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.