Triple
T32091304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryan Street (Savannah, Georgia) |
E819599
|
entity |
| Predicate | hasLayoutRole |
P147625
|
FINISHED |
| Object | component of the orthogonal street grid of Savannah |
—
|
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: component of the orthogonal street grid of Savannah | Statement: [Bryan Street (Savannah, Georgia), hasLayoutRole, component of the orthogonal street grid of Savannah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLayoutRole Context triple: [Bryan Street (Savannah, Georgia), hasLayoutRole, component of the orthogonal street grid of Savannah]
-
A.
hasLayout
Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another entity.
-
B.
hasLayoutElement
Indicates that one entity includes, contains, or is associated with a specific layout element as part of its structural or visual arrangement.
-
C.
layoutRole
chosen
Indicates how an entity functions or is positioned within a larger structural or spatial arrangement.
-
D.
hasBorderRole
Indicates that an entity holds a specific functional or administrative role related to a border or boundary between regions or jurisdictions.
-
E.
hasEarlyScreenRole
Indicates that an entity played a role in an early stage of another entity’s screen-based career or production history.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 1, 2026, 12:25 a.m.