Triple
T4978141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tesla Backup Gateway |
E111817
|
entity |
| Predicate | installedLocation |
P3054
|
FINISHED |
| Object | residential buildings |
—
|
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 buildings | Statement: [Tesla Backup Gateway, installedLocation, residential buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installedLocation Context triple: [Tesla Backup Gateway, installedLocation, residential buildings]
-
A.
installationSpace
Indicates the physical or virtual area required or designated for installing an object, system, or component.
-
B.
repositoryLocation
Indicates the place or storage context where a repository is hosted, stored, or maintained.
-
C.
installedAt
chosen
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
D.
applicationLocation
Indicates the place or environment where an application is deployed, used, or made available.
-
E.
mountingLocation
Indicates the physical position or surface on which something is attached, fixed, or installed.
- 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_69bd441adc208190b70a033a0741d01e |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd7146e6e881908a55ab2756b631f6 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.