Triple
T25457337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania Route 23 |
E637946
|
entity |
| Predicate | nearbyNameVariant |
P161294
|
FINISHED |
| Object | Conshohocken State Road |
—
|
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: Conshohocken State Road | Statement: [Pennsylvania Route 23, nearbyNameVariant, Conshohocken State Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyNameVariant Context triple: [Pennsylvania Route 23, nearbyNameVariant, Conshohocken State Road]
-
A.
namedAfterNearbyPlace
Indicates that an entity’s name is derived from or inspired by a geographically nearby place.
-
B.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
C.
nameHasVariant
chosen
Indicates that an entity’s name has an alternative or variant form.
-
D.
neighboringAppellation
Indicates that two appellations (e.g., designated geographic areas) share a common boundary or are directly adjacent to each other.
-
E.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 21, 2026, 2:10 p.m.