Triple
T9714108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radar Operations Center (field presence) |
E235095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technical support organization |
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 support organization Context triple: [Radar Operations Center (field presence), instanceOf, technical support organization]
-
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 commission
A technical commission is a specialized group of experts formally appointed to study, evaluate, and provide recommendations on complex technical or scientific matters within a specific domain.
-
C.
telecommunications organization
A telecommunications organization is an entity that provides communication services and infrastructure—such as voice, data, and internet connectivity—across distances using wired, wireless, or satellite networks.
-
D.
information and communications technology organization
An information and communications technology organization is an entity that develops, manages, or delivers digital and networked technologies, services, and infrastructure to enable electronic communication, data processing, and information exchange.
-
E.
Supporting Organization
A Supporting Organization is an entity that exists primarily to provide resources, services, or assistance to another organization in order to help it achieve its goals.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:19 p.m.