Triple
T7832025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Canal (Lawrence, Massachusetts) |
E181593
|
entity |
| Predicate | transportOf |
P2059
|
FINISHED |
| Object | water for power, not navigation |
—
|
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 for power, not navigation | Statement: [North Canal (Lawrence, Massachusetts), transportOf, water for power, not navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportOf Context triple: [North Canal (Lawrence, Massachusetts), transportOf, water for power, not navigation]
-
A.
transportFrom
Indicates that something or someone is moved or carried away starting from a specified origin location.
-
B.
transportFor
Indicates a relationship where one entity serves as the means or service used to move another entity from one place to another.
-
C.
transportAgnostic
Indicates that the relationship or action is independent of, and unaffected by, the specific transport mechanism or communication channel used.
-
D.
transports
chosen
Indicates that one entity carries or conveys another entity from one place to another.
-
E.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
- 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb0648bb308190a34fbcd81ff6fda2 |
completed | March 30, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:44 p.m.