Triple
T8051608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Gateway Port |
E187685
|
entity |
| Predicate | hasStorageType |
P32186
|
FINISHED |
| Object | container yard |
—
|
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: container yard | Statement: [London Gateway Port, hasStorageType, container yard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStorageType Context triple: [London Gateway Port, hasStorageType, container yard]
-
A.
hasStorageClass
Indicates that one entity is assigned or associated with a particular storage class that defines how its data is stored or managed.
-
B.
hasVaultType
Indicates that an entity is associated with or classified by a particular type or category of vault.
-
C.
hasCapacityType
Indicates that an entity possesses a specific kind or classification of capacity or capability.
-
D.
hasSpaceType
chosen
Indicates that one entity is associated with, or classified by, a particular type or category of space.
-
E.
supportsDatastoreType
Indicates that one entity is capable of working with, handling, or being compatible with a specified type of datastore.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f7aab6481909d4a7cb9eabcd2af |
completed | March 31, 2026, 3:28 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:24 p.m.