Triple
T7347377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badrashin district |
E169412
|
entity |
| Predicate | governorateCapitalDistance |
P10889
|
FINISHED |
| Object | south of Giza city |
—
|
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: south of Giza city | Statement: [Badrashin district, governorateCapitalDistance, south of Giza city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governorateCapitalDistance Context triple: [Badrashin district, governorateCapitalDistance, south of Giza city]
-
A.
hasCountyCapitalDistance
Indicates a distance relationship specifying how far a county is from its capital.
-
B.
stateCapitalProximity
Indicates the spatial closeness or distance between a state’s capital city and another specified location.
-
C.
distanceFromCapital
chosen
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
D.
governorateCapitalAlsoCapitalOf
Indicates that a city serving as the capital of a governorate is also the capital of another administrative unit or jurisdiction.
-
E.
governorateSeat
Indicates the city or town that serves as the administrative center or 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_69c68a5878888190968ce4d04db8d69f |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f139505c8190a7158cf59a6e089e |
completed | March 27, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69c6f02aeeb8819099d1626566cec18b |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:05 p.m.