Triple
T10856872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bramley-Moore Dock |
E256289
|
entity |
| Predicate | futureUse |
P12134
|
FINISHED |
| Object | football stadium site |
—
|
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: football stadium site | Statement: [Bramley-Moore Dock, futureUse, football stadium site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureUse Context triple: [Bramley-Moore Dock, futureUse, football stadium site]
-
A.
futureServes
Indicates that, at a future time, one entity will perform a service or act in a serving role for another entity.
-
B.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
C.
futureComponentOf
Indicates that one entity is expected or planned to become a component or part of another entity at some point in the future.
-
D.
plannedUseOf
chosen
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
E.
laterFeature
Indicates that one feature, event, or element occurs or is introduced after another in time.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7513695ac8190b5812e977a422c37 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.