Triple
T15015415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sleaford Navigation |
E377946
|
entity |
| Predicate | closedForNavigation |
P116367
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Sleaford Navigation, closedForNavigation, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedForNavigation Context triple: [Sleaford Navigation, closedForNavigation, 20th century]
-
A.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
B.
closedDuring
Indicates that an entity is not open or available for use during a specified time period or under certain conditions.
-
C.
closedForSafety
Indicates that an entity (such as a place, facility, or route) is temporarily unavailable or inaccessible due to safety concerns or hazards.
-
D.
closedToPublic
Indicates that access to the referenced entity is restricted so that the general public is not allowed to enter or use it.
-
E.
closedBy
Indicates that one entity performs the action of closing, finishing, or terminating another entity (such as a task, issue, or process).
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7623c3c819092ca36b358b01842 |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:55 a.m.