Triple
T23285250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Charles Street |
E588967
|
entity |
| Predicate | roadNameContains |
P5943
|
FINISHED |
| Object | Charles Street |
—
|
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: Charles Street | Statement: [North Charles Street, roadNameContains, Charles Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadNameContains Context triple: [North Charles Street, roadNameContains, Charles Street]
-
A.
roadName
chosen
Indicates the specific name assigned to a road that identifies it within a transportation or address system.
-
B.
roadNameAlongRoute
Indicates that a specific road name is associated with, or used along, a particular segment or portion of a route.
-
C.
streetAddressContains
Indicates that one street address string includes another address-related string as a substring or component.
-
D.
isNamedRoadIn
Indicates that a specific named road is located within or belongs to a particular geographic area or region.
-
E.
roadNameSharedWith
Indicates that two or more roads share the same name.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1964600888190b40ecbefdc8aec64 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:59 p.m.