Triple
T10653741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Killarney, Johannesburg |
E251035
|
entity |
| Predicate | typicalDwelling |
P542
|
FINISHED |
| Object | multi-storey flats |
—
|
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: multi-storey flats | Statement: [Killarney, Johannesburg, typicalDwelling, multi-storey flats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDwelling Context triple: [Killarney, Johannesburg, typicalDwelling, multi-storey flats]
-
A.
typicalHouse
Indicates that something is a standard or representative example of a house in terms of its usual features, structure, or characteristics.
-
B.
residenceType
chosen
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
C.
typicalUnitType
Indicates that one entity is the standard or commonly used unit type associated with measuring or expressing the other entity.
-
D.
housingPattern
Indicates the typical arrangement or distribution of housing units or residential structures within a given area or context.
-
E.
houseTypeLower
Indicates that one entity has a house type that is considered lower or less than another entity’s house type in some defined ordering or hierarchy.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dff85674819099bf40c9f4fede15 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:06 p.m.