Triple
T19110185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manor Ground |
E467766
|
entity |
| Predicate | postUse |
P134450
|
FINISHED |
| Object | redeveloped for housing |
—
|
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: redeveloped for housing | Statement: [Manor Ground, postUse, redeveloped for housing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postUse Context triple: [Manor Ground, postUse, redeveloped for housing]
-
A.
post2003Use
Indicates that something is used, applied, or in effect during the period after the year 2003.
-
B.
postExpulsionUse
Indicates the use or treatment of something after it has been expelled, removed, or discharged from its original context or container.
-
C.
postReunificationUse
Indicates how something is used or purposed after a reunification has taken place.
-
D.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
E.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
- F. None of above. chosen
Provenance (4 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e393bafc81908e35a0eba7b807a6 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.