Triple
T15851028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Measure R (Los Angeles County) |
E384337
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation sales tax ordinance |
C25454
|
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: transportation sales tax ordinance Context triple: [Measure R (Los Angeles County), instanceOf, transportation sales tax ordinance]
-
A.
transportation standard
A transportation standard is an agreed-upon set of rules, specifications, and protocols that ensure compatibility, safety, and efficiency across transportation systems, vehicles, and infrastructure.
-
B.
local tax
Local tax is a compulsory financial charge imposed by municipal or regional authorities on individuals, businesses, or property within their jurisdiction to fund local public services and infrastructure.
-
C.
transportation safety law
Transportation safety law is the body of legal rules and regulations designed to prevent accidents and injuries in all modes of transport by setting safety standards, enforcing compliance, and assigning liability for violations.
-
D.
public transport pricing scheme
A public transport pricing scheme is a structured set of rules and fares that determines how passengers are charged for using public transit services based on factors such as distance, time, mode, and user category.
-
E.
transportation funding measure
chosen
A transportation funding measure is a policy instrument, often a ballot initiative or legislative act, that authorizes and allocates dedicated revenue sources to plan, build, operate, and maintain transportation infrastructure and services.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:50 a.m.