Triple
T24553331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concord Junction |
E607434
|
entity |
| Predicate | hasStreetPatternInfluencedBy |
P156292
|
FINISHED |
| Object | railroad alignments |
—
|
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: railroad alignments | Statement: [Concord Junction, hasStreetPatternInfluencedBy, railroad alignments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetPatternInfluencedBy Context triple: [Concord Junction, hasStreetPatternInfluencedBy, railroad alignments]
-
A.
hasStreetGridPattern
Indicates that an area’s street layout follows a structured, grid-like pattern of intersecting roads.
-
B.
hasPavementPattern
Indicates that an entity possesses or is characterized by a specific pattern or design in its pavement surface.
-
C.
hasStreetNamingPattern
Indicates that there is a characteristic or systematic way in which streets are named in relation to a given entity.
-
D.
hasNearbyStreetPattern
Indicates that one location has a street layout or configuration that is spatially close to, or in the vicinity of, another location’s street pattern.
-
E.
streetscapeStyle
Indicates the characteristic visual and design style that defines the overall appearance and layout of a street and its surrounding public realm.
- F. None of above. chosen
Provenance (4 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_69e2c4cae1b88190825e88d5ce8aa61e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8cf1ef88190977da0fb79796616 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:27 a.m.