Triple
T31394038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stroudwater Navigation |
E800814
|
entity |
| Predicate | abandonmentAct |
P140249
|
FINISHED |
| Object | 1954 |
—
|
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: 1954 | Statement: [Stroudwater Navigation, abandonmentAct, 1954]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abandonmentAct Context triple: [Stroudwater Navigation, abandonmentAct, 1954]
-
A.
abandonment
Indicates the act of one party leaving, forsaking, or giving up responsibility for another party or thing.
-
B.
abandonmentType
Indicates the specific manner or category of how something or someone was abandoned in the described situation.
-
C.
abandons
chosen
Indicates that one entity leaves, deserts, or gives up responsibility for another entity or activity, ceasing support, care, or involvement.
-
D.
abandonmentStart
Indicates the point in time or event at which an abandonment process or state begins between the involved entities.
-
E.
abandonedBy
Indicates that one entity has been deserted, forsaken, or left behind by another entity that was previously present, responsible, or involved.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:19 p.m.