Triple
T26687252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amoskeag Dam |
E672779
|
entity |
| Predicate | builtToHarness |
P141276
|
FINISHED |
| Object | Amoskeag Falls |
—
|
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: Amoskeag Falls | Statement: [Amoskeag Dam, builtToHarness, Amoskeag Falls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtToHarness Context triple: [Amoskeag Dam, builtToHarness, Amoskeag Falls]
-
A.
builtToMark
Indicates that something was constructed for the purpose of commemorating, signaling, or designating a particular event, place, boundary, or significance.
-
B.
harnesses
chosen
Indicates that one entity effectively utilizes, controls, or channels the power, resources, or capabilities of another for a particular purpose.
-
C.
builtThrough
Indicates that something was created, developed, or achieved by means of a specified method, process, or intermediary.
-
D.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
E.
builtDevice
Indicates that one entity constructed or assembled a device for or associated with another entity.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 3:23 a.m.