Triple
T13218282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania Route 228 |
E314678
|
entity |
| Predicate | connectsTypeOfRoutes |
P13416
|
FINISHED |
| Object | regional routes |
—
|
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: regional routes | Statement: [Pennsylvania Route 228, connectsTypeOfRoutes, regional routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsTypeOfRoutes Context triple: [Pennsylvania Route 228, connectsTypeOfRoutes, regional routes]
-
A.
routerTypes
Indicates that one entity specifies or categorizes the types or kinds of routers associated with another entity.
-
B.
connectsDestinationType
Indicates that one entity serves as a connection or link specifically to a destination of a given type.
-
C.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
D.
routesFrom
Indicates that something (such as a path, connection, or communication) originates at one entity and is directed or carried from that source entity toward another.
-
E.
includesRouteType
chosen
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf392e08190949ee4d194566395 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:18 p.m.