Triple
T28379844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siemens SWT-3.6-120 |
E718859
|
entity |
| Predicate | gridUse |
P92159
|
FINISHED |
| Object | utility grid supply |
—
|
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: utility grid supply | Statement: [Siemens SWT-3.6-120, gridUse, utility grid supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridUse Context triple: [Siemens SWT-3.6-120, gridUse, utility grid supply]
-
A.
gridUsage
chosen
Indicates how much and in what way an entity consumes or relies on a shared grid-based resource, such as an electrical or data grid.
-
B.
gridService
Indicates a relationship where an entity provides, manages, or participates in services related to an electrical or utility grid infrastructure.
-
C.
sectorUsage
Indicates how a particular sector is utilized or engaged in a given context or activity.
-
D.
gridRegion
Indicates a spatial relationship where an entity is located within, or associated with, a specific region or cell of a grid.
-
E.
arenaUsed
Indicates that a particular arena or venue is utilized or has been employed for a specific event, activity, or purpose.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64cb538448190be1c85c33d6bdd62 |
completed | May 2, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:05 a.m.