Triple
T3695113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seabrook |
E78438
|
entity |
| Predicate | roadNetworkServes |
P18987
|
FINISHED |
| Object | local streets of Mashpee |
—
|
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 streets of Mashpee | Statement: [Seabrook, roadNetworkServes, local streets of Mashpee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadNetworkServes Context triple: [Seabrook, roadNetworkServes, local streets of Mashpee]
-
A.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
-
B.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
C.
roadNetworkPartOf
Indicates that one road network segment or component is a constituent part of a larger road network.
-
D.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
E.
roadNetworkHubOf
chosen
Indicates that one location functions as a central node or hub within the road network relative to another location or area.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4eafd348190986f69aee787fd8f |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.