Triple
T20411965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Portbury Dock |
E500606
|
entity |
| Predicate | hasStorageFor |
P85952
|
FINISHED |
| Object | new vehicles |
—
|
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: new vehicles | Statement: [Royal Portbury Dock, hasStorageFor, new vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStorageFor Context triple: [Royal Portbury Dock, hasStorageFor, new vehicles]
-
A.
hasStorage
chosen
Indicates that one entity provides or contains storage capacity or space for another entity or resource.
-
B.
hasStorageFunction
Indicates that an entity serves to store, retain, or hold another entity or resource for later use.
-
C.
hasStorageClass
Indicates that one entity is assigned or associated with a particular storage class that defines how its data is stored or managed.
-
D.
hasMemoryIn
Indicates that an entity possesses or stores memory, information, or experiences within a specified context, location, or medium.
-
E.
hasStorageRing
Indicates that one entity possesses or is equipped with a storage ring associated with it.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a3f8fdc8190b05b6c41b38f34b7 |
completed | April 20, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.