Triple
T20600333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evergreen Point Bridge |
E506159
|
entity |
| Predicate | tollingResumed |
P119413
|
FINISHED |
| Object | 2016-04-25 |
—
|
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: 2016-04-25 | Statement: [Evergreen Point Bridge, tollingResumed, 2016-04-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tollingResumed Context triple: [Evergreen Point Bridge, tollingResumed, 2016-04-25]
-
A.
tollingBegan
Indicates that the period during which a time limit or deadline is suspended or paused has started.
-
B.
tollStatusChange
chosen
Indicates a change in the toll-related status or condition associated with an entity, such as the start, end, or modification of a toll requirement.
-
C.
tollingType
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
-
D.
tollingAuthority
Indicates the entity that has the authority to impose, collect, or manage a toll on a given route, facility, or service.
-
E.
tollIntroduced
Indicates that a toll was established or put into effect for using a particular route, facility, or service.
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1ef9ac8190b05e23c149529cb9 |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.