Triple
T10003519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HydroFit elevator |
E198183
|
entity |
| Predicate | installationLocation |
P39280
|
FINISHED |
| Object | elevator shaft |
—
|
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: elevator shaft | Statement: [HydroFit elevator, installationLocation, elevator shaft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installationLocation Context triple: [HydroFit elevator, installationLocation, elevator shaft]
-
A.
installationSpace
chosen
Indicates the physical or virtual area required or designated for installing an object, system, or component.
-
B.
deploymentLocation
Indicates the place or environment where something (such as a system, resource, or component) is deployed or put into operational use.
-
C.
repositoryLocation
Indicates the place or storage context where a repository is hosted, stored, or maintained.
-
D.
installedAt
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
E.
launchLocation
Indicates the place or site from which something is launched or set into motion.
- 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_69ca830fcca48190bbbd9b20c233835f |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd12f6488190bd5257b5f65437cc |
completed | April 2, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69cd1da2cf9081908a6c0eb5247d0bc2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:51 p.m.