Triple
T14944588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yarmouk |
E372622
|
entity |
| Predicate | hasRoadLayoutType |
P74765
|
FINISHED |
| Object | grid-like street pattern |
—
|
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: grid-like street pattern | Statement: [Yarmouk, hasRoadLayoutType, grid-like street pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadLayoutType Context triple: [Yarmouk, hasRoadLayoutType, grid-like street pattern]
-
A.
hasRoadConfiguration
Indicates that there exists a specific arrangement or layout of roads associated with or characterizing an entity.
-
B.
hasRoadNetworkType
chosen
Indicates the type or classification of road network associated with or present in an entity.
-
C.
hasUrbanLayoutType
Indicates that an entity possesses or is characterized by a specific type or pattern of urban spatial layout.
-
D.
hasRoadComponent
Indicates that something includes, contains, or is composed of a specific road-related part or element.
-
E.
hasRoadCharacteristics
Indicates that one entity possesses specific road-related features or attributes, such as type, condition, or structural properties.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded68d20048190a403af85fe43dede |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:39 a.m.