Triple
T37520110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butlers Lane area |
E932745
|
entity |
| Predicate | typicalHousingEra |
P6333
|
FINISHED |
| Object | 20th century 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: 20th century housing | Statement: [Butlers Lane area, typicalHousingEra, 20th century housing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHousingEra Context triple: [Butlers Lane area, typicalHousingEra, 20th century housing]
-
A.
housingTypeHistoric
Indicates that an entity’s housing type is classified based on historical or heritage-related characteristics.
-
B.
urbanDevelopmentEra
Indicates the historical period or phase during which significant urban development or transformation of a place occurred.
-
C.
estateTypeHistorically
Indicates that one entity historically had a particular type or classification of estate, even if that estate type may have changed or no longer exists in the present.
-
D.
constructionCentury
chosen
Indicates the century during which something was constructed or built.
-
E.
typicalCenturySize
Indicates the usual or characteristic number of items or units that make up a century in a given context.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.