Triple
T26745180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tel-el-Kebir |
E674377
|
entity |
| Predicate | hasApproximateDistanceToCairo |
P39009
|
FINISHED |
| Object | about 110 km northeast of Cairo |
—
|
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: about 110 km northeast of Cairo | Statement: [Tel-el-Kebir, hasApproximateDistanceToCairo, about 110 km northeast of Cairo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateDistanceToCairo Context triple: [Tel-el-Kebir, hasApproximateDistanceToCairo, about 110 km northeast of Cairo]
-
A.
distanceFromCairo
Indicates the measured spatial distance between a given entity’s location and the city of Cairo.
-
B.
distanceToCairo_km
chosen
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Cairo.
-
C.
distanceFromGizaPlateau
Indicates the measured spatial distance between a given location and the Giza Plateau.
-
D.
distanceFromFaiyum
Indicates the spatial distance between a given location and the Faiyum region.
-
E.
distanceToEgyptianBorder
Indicates the measured distance between a given location and the border of Egypt.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 27, 2026, 3:51 a.m.