Triple
T2310059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bramley-Moore Dock stadium development |
E51932
|
entity |
| Predicate | usesSite |
P1205
|
FINISHED |
| Object | former commercial dockland |
—
|
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: former commercial dockland | Statement: [Bramley-Moore Dock stadium development, usesSite, former commercial dockland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSite Context triple: [Bramley-Moore Dock stadium development, usesSite, former commercial dockland]
-
A.
currentSiteUse
Indicates how a site is presently being used or the function it currently serves.
-
B.
site
chosen
Indicates that one entity is the physical or virtual location where another entity is situated, occurs, or is based.
-
C.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
D.
isSiteSpecific
Indicates that something is designed, intended, or valid only for a particular location, context, or site and does not generally apply elsewhere.
-
E.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.