Triple
T21506689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reports on transportation rates and discrimination |
E530614
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory investigation |
C22261
|
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: regulatory investigation Context triple: [Reports on transportation rates and discrimination, instanceOf, regulatory investigation]
-
A.
official investigation
An official investigation is a formal, authorized inquiry conducted by a competent authority to gather facts, determine the truth, and assess responsibility regarding a specific incident, allegation, or issue.
-
B.
regulatory activity
chosen
Regulatory activity is the process by which an entity establishes, interprets, or enforces rules and standards to guide or control the behavior of systems, organizations, or individuals.
-
C.
federal investigation
A federal investigation is a formal inquiry conducted by national government agencies to gather evidence, determine whether federal laws have been violated, and support potential enforcement or prosecution actions.
-
D.
judicial investigation
A judicial investigation is a formal, legally authorized inquiry conducted by judicial authorities to gather, examine, and evaluate evidence in order to determine whether laws have been violated and if legal proceedings should follow.
-
E.
regulatory authority
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:24 p.m.