Triple
T19345533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenland Dock |
E483865
|
entity |
| Predicate | closureAsCommercialDock |
P65693
|
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: [Greenland Dock, closureAsCommercialDock, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureAsCommercialDock Context triple: [Greenland Dock, closureAsCommercialDock, 20th century]
-
A.
docking
Indicates the action of one vehicle or structure aligning and securely connecting to another for transfer, access, or support.
-
B.
closureBy
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or process.
-
C.
operatedDock
Indicates that an entity managed or controlled the functioning of a dock or docking facility.
-
D.
closureType
chosen
Indicates the specific manner or condition in which something is closed, completed, or terminated within a process or relationship.
-
E.
dockIncludes
Indicates that a dock contains, encompasses, or has as part of its structure the specified element or component.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185a56b4819089336564959b84df |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.