Triple
T24727410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Victoria Dock |
E618190
|
entity |
| Predicate | closedForCommercialShipping |
P135135
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Royal Victoria Dock, closedForCommercialShipping, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedForCommercialShipping Context triple: [Royal Victoria Dock, closedForCommercialShipping, 1980s]
-
A.
closedToCommercialShipping
chosen
Indicates that an area or route is not accessible for use by commercial shipping vessels.
-
B.
closedToGoods
Indicates that an entity (such as a route, border, or facility) is not open or available for the movement, trade, or handling of goods.
-
C.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
D.
closedOffFrom
Indicates that one entity is isolated, blocked, or prevented from accessing, interacting with, or being influenced by another entity.
-
E.
closedForDistilling
Indicates that an entity is temporarily unavailable or shut down because it is being used for distilling operations.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4 a.m.