Triple
T3624205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beni Suef |
E76796
|
entity |
| Predicate | hasGeographicalOrientation |
P12663
|
FINISHED |
| Object | south 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: south of Cairo | Statement: [Beni Suef, hasGeographicalOrientation, south of Cairo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeographicalOrientation Context triple: [Beni Suef, hasGeographicalOrientation, south of Cairo]
-
A.
hasRegionalOrientation
Indicates that an entity is oriented toward, focused on, or primarily associated with a specific geographic region.
-
B.
hasGeographyCharacteristic
Indicates that an entity possesses a specific geographical feature, property, or attribute.
-
C.
geographicContext
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
D.
hasOrientation
chosen
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
E.
orientationInducedBy
Indicates that the orientation of one entity is determined or caused by the orientation or configuration of another entity.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2d9845c8190ad65b2471000dfa0 |
completed | March 8, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.