Triple
T28863130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arab League Street |
E728917
|
entity |
| Predicate | nearbyMajorThoroughfare |
P49834
|
FINISHED |
| Object | Gamaet El Dowal El Arabia Street |
—
|
NE NERFINISHED |
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: Gamaet El Dowal El Arabia Street | Statement: [Arab League Street, nearbyMajorThoroughfare, Gamaet El Dowal El Arabia Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyMajorThoroughfare Context triple: [Arab League Street, nearbyMajorThoroughfare, Gamaet El Dowal El Arabia Street]
-
A.
nearbyMajorRoad
chosen
Indicates that one entity is located close to a significant or heavily used road.
-
B.
hasNearbyStreet
Indicates that one entity is located close to or adjacent to a street.
-
C.
nearestRoadHead
Indicates that one location is the closest accessible road endpoint (or road access point) to another location.
-
D.
isThoroughfareFor
Indicates that something serves as a route or passageway used for travel or transportation between places.
-
E.
avenueRadiatingFrom
Indicates that one avenue extends outward from and is oriented away from another central point or thoroughfare, like a spoke radiating from a hub.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 28, 2026, 6:48 a.m.