Triple
T28217584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bühnenservice Berlin |
E711356
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technical service provider |
C25606
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: technical service provider Context triple: [Bühnenservice Berlin, instanceOf, technical service provider]
-
A.
technical services organization
chosen
A technical services organization is a specialized entity that provides expert engineering, IT, and other technology-focused support, solutions, and maintenance to help clients design, implement, and operate complex systems.
-
B.
technical emergency service
A technical emergency service is an organized unit that responds to and manages incidents involving technical hazards, infrastructure failures, and specialized rescue operations using expert equipment and skills.
-
C.
technical information service
A technical information service is a specialized support function that collects, manages, and delivers accurate, up-to-date technical data and guidance to users, customers, or internal stakeholders to assist with problem-solving and decision-making.
-
D.
technical personnel
Technical personnel are individuals with specialized knowledge and skills who install, operate, maintain, or support technical systems, equipment, or processes within an organization.
-
E.
technical expert
A technical expert is a highly skilled individual with deep, specialized knowledge in a particular technical domain who can analyze complex problems and provide effective, evidence-based solutions.
- F. None of above.
Provenance (1 batch)
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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:44 p.m.