Triple
T14193166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edgbaston, Birmingham, England |
E351763
|
entity |
| Predicate | styleOfHousing |
P4631
|
FINISHED |
| Object | Victorian villas |
—
|
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: Victorian villas | Statement: [Edgbaston, Birmingham, England, styleOfHousing, Victorian villas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOfHousing Context triple: [Edgbaston, Birmingham, England, styleOfHousing, Victorian villas]
-
A.
keeperHouseStyle
Indicates the architectural or design style associated with a keeper’s house (e.g., lighthouse keeper’s residence).
-
B.
housingPattern
Indicates the typical arrangement or distribution of housing units or residential structures within a given area or context.
-
C.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
D.
architectureType
chosen
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
E.
hasTraditionalHouseStyle
Indicates that an entity possesses or is characterized by a traditional style of house or residential architecture.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61e0a52081908213aa6e548d4418 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:04 a.m.