Triple
T107217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Falls, Newton |
E2163
|
entity |
| Predicate | historicallyDevelopedAround |
P283
|
FINISHED |
| Object | water-powered mills on the Charles River |
—
|
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: water-powered mills on the Charles River | Statement: [Lower Falls, Newton, historicallyDevelopedAround, water-powered mills on the Charles River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyDevelopedAround Context triple: [Lower Falls, Newton, historicallyDevelopedAround, water-powered mills on the Charles River]
-
A.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
B.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
C.
developedAlong
Indicates that something was created, constructed, or evolved following the course, path, or boundary of something else.
-
D.
developedAt
chosen
Indicates the place or location where something was created, built, or developed.
-
E.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a25a1199ac8190ac65ffaaf45b4f5b |
completed | Feb. 28, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69a2563e7188819091e9a94e071991d7 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.