Triple
T34166325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Side Bridge (Charleston) |
E876421
|
entity |
| Predicate | accessesNeighborhood |
P182285
|
FINISHED |
| Object | South Hills |
—
|
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: South Hills | Statement: [South Side Bridge (Charleston), accessesNeighborhood, South Hills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessesNeighborhood Context triple: [South Side Bridge (Charleston), accessesNeighborhood, South Hills]
-
A.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
B.
neighborhood
Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
-
C.
hasNeighborhoodAssociation
Indicates that an entity is associated with, or falls under the jurisdiction of, a particular neighborhood association.
-
D.
partOfNeighborhoodNetwork
Indicates that an entity belongs to, or is included within, a specific neighborhood’s interconnected network or system.
-
E.
neighborhoodView
Indicates that an entity has a view overlooking or prominently featuring the surrounding neighborhood or nearby residential area.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: May 1, 2026, 1:54 a.m.