Triple
T16999073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erskine Bridge |
E412390
|
entity |
| Predicate | previouslyHadToll |
P126111
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Erskine Bridge, previouslyHadToll, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyHadToll Context triple: [Erskine Bridge, previouslyHadToll, yes]
-
A.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
B.
hasTollSegment
Indicates that a route, road, or path includes a segment where a toll must be paid.
-
C.
appliesTollTo
Indicates that a fee or charge is imposed on a subject for using, accessing, or passing through something.
-
D.
tollIntroduced
Indicates that a toll was established or put into effect for using a particular route, facility, or service.
-
E.
hasTollVariant
Indicates that an entity has a version or instance that requires paying a toll or fee for use or access.
- F. None of above. chosen
Provenance (4 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d37cd6248190a7202ae754882640 |
completed | April 18, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e378e037c88190935d732e0f10d5d7 |
completed | April 18, 2026, 12:28 p.m. |
Created at: April 10, 2026, 5:32 a.m.