Triple
T32271592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NC Quick Pass |
E824426
|
entity |
| Predicate | regulatesTollingOn |
P78245
|
FINISHED |
| Object | North Carolina Turnpike Authority facilities |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: North Carolina Turnpike Authority facilities | Statement: [NC Quick Pass, regulatesTollingOn, North Carolina Turnpike Authority facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesTollingOn Context triple: [NC Quick Pass, regulatesTollingOn, North Carolina Turnpike Authority facilities]
-
A.
tollingType
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
-
B.
tollingAuthority
chosen
Indicates the entity that has the authority to impose, collect, or manage a toll on a given route, facility, or service.
-
C.
tollingBegan
Indicates that the period during which a time limit or deadline is suspended or paused has started.
-
D.
appliesTollTo
Indicates that a fee or charge is imposed on a subject for using, accessing, or passing through something.
-
E.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
- F. None of above.
Provenance (3 batches)
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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 1, 2026, 12:42 a.m.