Triple
T23989099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SUSHI |
E605014
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | usage statistics harvesting protocol |
C48759
|
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: usage statistics harvesting protocol Context triple: [SUSHI, instanceOf, usage statistics harvesting protocol]
-
A.
connectivity measurement framework
A connectivity measurement framework is a structured system of methods, metrics, and tools used to quantify, analyze, and compare the quality, reliability, and performance of connections within a network or between distributed components.
-
B.
mobile device tracking service
A mobile device tracking service is a system that continuously monitors, records, and reports the real-time or historical locations and movement patterns of mobile devices for purposes such as security, analytics, and asset management.
-
C.
regulatory statistics unit
A regulatory statistics unit is a specialized team that applies statistical methods to support regulatory decision-making, compliance evaluation, and policy development by analyzing and interpreting relevant data.
-
D.
Internet access toolkit
A comprehensive set of hardware, software, and configuration utilities that enables users or systems to establish, manage, and troubleshoot connections to the internet.
-
E.
standardized service access point
A standardized service access point is a well-defined interface through which clients uniformly request and consume a specific set of services, independent of underlying implementations or locations.
- F. None of above. chosen
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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:37 p.m.