Triple
T11304158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hells Gate fishways area rapids |
E267671
|
entity |
| Predicate | hasManMadeModification |
P61330
|
FINISHED |
| Object | concrete fish ladders |
—
|
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: concrete fish ladders | Statement: [Hells Gate fishways area rapids, hasManMadeModification, concrete fish ladders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManMadeModification Context triple: [Hells Gate fishways area rapids, hasManMadeModification, concrete fish ladders]
-
A.
hasHumanModification
chosen
Indicates that an entity has been altered, influenced, or modified as a result of human activity or intervention.
-
B.
hasManMadeOrigin
Indicates that something originates from or is created by human activity rather than occurring naturally.
-
C.
isModifiedAs
Indicates that an entity has been altered or changed from its original state in some specified manner.
-
D.
hasManual
Indicates that an entity is associated with a manual that provides instructions or documentation for it.
-
E.
showsModificationBy
Indicates that one entity displays or reveals the changes, alterations, or modifications that have been made by 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a5c3788190ba54eda514b97903 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.