Triple
T2292432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suez |
E51534
|
entity |
| Predicate | distanceToCairo_km |
P39009
|
FINISHED |
| Object | approximately 120 |
—
|
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: approximately 120 | Statement: [Suez, distanceToCairo_km, approximately 120]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToCairo_km Context triple: [Suez, distanceToCairo_km, approximately 120]
-
A.
distanceFromCairo
Indicates the measured spatial distance between a given entity’s location and the city of Cairo.
-
B.
distanceFromAlexandria_km
Indicates the distance, measured in kilometers, between a given location and Alexandria.
-
C.
distanceToBudapest_km
Indicates the physical distance, measured in kilometers, between a given location and Budapest.
-
D.
distanceFromBaghdad
Indicates the spatial distance between a given location or entity and the city of Baghdad.
-
E.
distanceToKinshasa
Indicates the measured spatial distance between a given entity’s location and the city of Kinshasa.
- F. None of above. chosen
Provenance (4 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcd0e42248190ada33b84d75caa64 |
completed | March 7, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69abc589295c819092989820c2b4e9d8 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcd0d01ac8190935fe904905cb233 |
completed | March 7, 2026, 7 a.m. |
Created at: March 4, 2026, 7:48 p.m.