Triple
T4305407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Home House, London |
E99943
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic townhouse |
C5702
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historic townhouse Context triple: [Home House, London, instanceOf, historic townhouse]
-
A.
historic estate
A historic estate is a large, significant property—often including a grand residence, outbuildings, and landscaped grounds—that holds cultural, architectural, or historical importance from a past era.
-
B.
historic town
A historic town is a settlement characterized by preserved architecture, landmarks, and cultural features that reflect significant events, periods, or traditions from the past.
-
C.
historic township
A historic township is a former or long-established local administrative or geographic subdivision, often with distinct historical boundaries, governance, and community identity that may differ from modern municipal structures.
-
D.
Historic house
chosen
A historic house is a residential building recognized for its significant architectural, cultural, or historical value, often preserved or restored to reflect the period in which it was built.
-
E.
historic estate type
A historic estate type is a classification of large, historically significant residential properties characterized by their architectural style, period of construction, original function, and cultural or social importance.
- F. None of above.
Provenance (1 batch)
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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:09 p.m.