Triple
T34541376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siemens BS-11 |
E886814
|
entity |
| Predicate | typicalBand |
P53870
|
FINISHED |
| Object | GSM 900 |
—
|
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: GSM 900 | Statement: [Siemens BS-11, typicalBand, GSM 900]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBand Context triple: [Siemens BS-11, typicalBand, GSM 900]
-
A.
band
Indicates that multiple entities join together to form a unified group, typically for a shared purpose or activity.
-
B.
bands
Indicates that multiple entities join together to form a group or collective unit.
-
C.
producerBand
Indicates that one band serves as the producer (overseeing or managing the creation and recording) of another band’s music or releases.
-
D.
hasBand
Indicates that an entity is associated with or includes a particular band (e.g., musical group or band-like unit).
-
E.
usesBand
chosen
Indicates that one entity employs or makes use of a particular band (such as a group, frequency band, or band resource) in performing an action or fulfilling a function.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:02 a.m.