Triple
T10653749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Killarney, Johannesburg |
E251035
|
entity |
| Predicate | buildingForm |
P32038
|
FINISHED |
| Object | sectional title schemes |
—
|
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: sectional title schemes | Statement: [Killarney, Johannesburg, buildingForm, sectional title schemes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingForm Context triple: [Killarney, Johannesburg, buildingForm, sectional title schemes]
-
A.
constructionForm
chosen
Indicates the method, style, or structural technique by which something is built or constructed.
-
B.
buildingStructure
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of another entity.
-
C.
buildingSection
Indicates a relationship where one entity is a specific section, part, or subdivision of a larger building.
-
D.
building
Indicates that one entity constructs, assembles, or develops another entity, typically over a period of time.
-
E.
buildingSystem
Indicates that one entity functions as a system, subsystem, or organized set of components that serves or supports the operation of a building.
- 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.