Triple
T14375806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crawley Court |
E356470
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | communications facility |
C10698
|
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: communications facility Context triple: [Crawley Court, instanceOf, communications facility]
-
A.
telecommunications infrastructure component
A telecommunications infrastructure component is a physical or virtual element—such as cables, antennas, switches, or routers—that enables the transmission, routing, and management of voice, data, and multimedia communications across networks.
-
B.
infrastructure facility
chosen
An infrastructure facility is a physical installation or complex that provides essential services or support functions—such as transportation, utilities, communication, or public safety—necessary for the operation and development of a community or region.
-
C.
telecommunications network
A telecommunications network is a system of interconnected nodes, transmission media, and protocols that enables the exchange of voice, data, and multimedia information between users and devices over distance.
-
D.
communications unit
A communications unit is a modular component responsible for managing, formatting, and transmitting information between systems, devices, or subsystems using defined communication protocols.
-
E.
deep space communications facility
A deep space communications facility is a ground-based complex equipped with large antennas, high-power transmitters, and sensitive receivers used to send commands to and receive data from spacecraft operating far beyond Earth's orbit.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:16 a.m.