Triple
T36213845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farringdon Within |
E1047633
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic ward |
C66147
|
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 ward Context triple: [Farringdon Within, instanceOf, historic ward]
-
A.
historic parish
A historic parish is a former ecclesiastical or civil territorial unit, typically centered around a church, whose boundaries and institutions reflect the administrative and social organization of a past period.
-
B.
historic block
A historic block is a contiguous group of buildings, streets, and public spaces recognized for their architectural, cultural, or historical significance and preserved to maintain their original character.
-
C.
historic subdistrict
A historic subdistrict is a geographically defined area within a larger district that contains a concentration of buildings, structures, or sites recognized for their historical, architectural, or cultural significance and is subject to preservation guidelines or protections.
-
D.
historic establishment
A historic establishment is a long-standing place of business or institution recognized for its significant role, continuity, and influence in a particular community or period of history.
-
E.
historicBuilding
A historicBuilding is a structure of significant age recognized for its cultural, architectural, or historical importance and often preserved or protected for future generations.
- F. None of above. chosen
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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.