Triple
T25457343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conshohocken State Road |
E637946
|
entity |
| Predicate | localDesignationOf |
P19168
|
FINISHED |
| Object | Pennsylvania Route 23 |
—
|
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: Pennsylvania Route 23 | Statement: [Conshohocken State Road, localDesignationOf, Pennsylvania Route 23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localDesignationOf Context triple: [Conshohocken State Road, localDesignationOf, Pennsylvania Route 23]
-
A.
communityDesignation
Indicates that an entity is formally assigned or recognized with a specific community-related status, label, or role.
-
B.
exampleDesignation
Indicates that one entity is identified or labeled as a representative or illustrative instance of another entity.
-
C.
environmentDesignation
Indicates that an entity is assigned a specific environmental classification or status within a given context.
-
D.
associatedDesignation
Indicates that one entity is linked to or identified by a particular designation, title, or label connected with it.
-
E.
mapDesignation
chosen
Indicates a formal label or identifier that is assigned to something specifically for use on a map.
- 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_69f5f72884408190b586de6cd827e1d4 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 2:10 p.m.