Triple
T1512310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phipps Street |
E32039
|
entity |
| Predicate | transportNetworkRole |
P25845
|
FINISHED |
| Object | local connector street in Charlestown |
—
|
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: local connector street in Charlestown | Statement: [Phipps Street, transportNetworkRole, local connector street in Charlestown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportNetworkRole Context triple: [Phipps Street, transportNetworkRole, local connector street in Charlestown]
-
A.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
B.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
C.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
-
D.
railNetworkRole
Indicates the specific function or responsibility an entity has within a rail network system.
-
E.
roadSystemRole
chosen
Indicates the specific functional role or responsibility an entity has within a road or transportation network system.
- 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_69a885e8caf88190a5fbb6159ce87786 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9396e16408190b5e7b0ac43376d81 |
completed | March 5, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69a907aa67cc81909f00135365447399 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.