Triple
T12089917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historic Town of St George and Related Fortifications |
E287913
|
entity |
| Predicate | hasBuildingTypes |
P50464
|
FINISHED |
| Object | residential houses |
—
|
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: residential houses | Statement: [Historic Town of St George and Related Fortifications, hasBuildingTypes, residential houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingTypes Context triple: [Historic Town of St George and Related Fortifications, hasBuildingTypes, residential houses]
-
A.
containsBuildingType
chosen
Indicates that a location or area includes at least one building of the specified type.
-
B.
hasBuildingHeightType
Indicates the classification or type used to characterize the height of a building in the relationship.
-
C.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
D.
hasBuildingFunction
Indicates that a building is used for or serves a particular function or purpose.
-
E.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.