Triple
T27105628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pawtucket Falls |
E686568
|
entity |
| Predicate | powerHarnessedBy |
P168586
|
FINISHED |
| Object | canals and millraces |
—
|
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: canals and millraces | Statement: [Pawtucket Falls, powerHarnessedBy, canals and millraces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerHarnessedBy Context triple: [Pawtucket Falls, powerHarnessedBy, canals and millraces]
-
A.
powerRange
Indicates the range of power values within which an entity operates, applies, or is considered valid.
-
B.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
C.
modeOfPower
Indicates the type or method of power or energy by which an entity operates or is driven.
-
D.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
E.
emitsMostEnergyIn
Indicates that one entity produces or radiates the greatest amount of its total energy output within the specified medium, range, or region represented by the other entity.
- 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 27, 2026, 8:50 a.m.