Triple
T5379220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 40 Bank Street |
E113037
|
entity |
| Predicate | hasBuildingServices |
P63641
|
FINISHED |
| Object | central HVAC |
—
|
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: central HVAC | Statement: [40 Bank Street, hasBuildingServices, central HVAC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingServices Context triple: [40 Bank Street, hasBuildingServices, central HVAC]
-
A.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
B.
hasBuildingStatus
Indicates the current condition, classification, or operational state assigned to a building.
-
C.
appliesToBuildingComplex
Indicates that something (such as a rule, condition, attribute, or action) is relevant or applicable to an entire building complex rather than to individual buildings or units.
-
D.
hasBuildingComponent
Indicates that one entity includes, contains, or is composed of another entity as a physical building component.
-
E.
hasMaintenanceFacilities
Indicates that one entity provides or contains facilities where the other entity can be serviced, repaired, or maintained.
- F. None of above. chosen
Provenance (4 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd887f5b0081909456992d1a071928 |
completed | March 20, 2026, 5:48 p.m. |
Created at: March 20, 2026, 2:03 p.m.