Triple
T35157613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clocktower Mall |
E1015168
|
entity |
| Predicate | hasBuildingTypeHistory |
P32919
|
FINISHED |
| Object | former Royal Navy warehouse |
—
|
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 Royal Navy warehouse | Statement: [Clocktower Mall, hasBuildingTypeHistory, former Royal Navy warehouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingTypeHistory Context triple: [Clocktower Mall, hasBuildingTypeHistory, former Royal Navy warehouse]
-
A.
hasFormerBuilding
Indicates that an entity previously occupied or used a different building, which is identified as its former building.
-
B.
hasTypeHistory
chosen
Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
-
C.
housingTypeHistoric
Indicates that an entity’s housing type is classified based on historical or heritage-related characteristics.
-
D.
containsBuildingType
Indicates that a location or area includes at least one building of the specified type.
-
E.
hasInfrastructureHistory
Indicates that there exists a record or account of past changes, developments, or states of infrastructure associated with an entity.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:02 p.m.