Triple
T13161703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Pontchartrain Causeway |
E312741
|
entity |
| Predicate | tollCollectionLocation |
P36751
|
FINISHED |
| Object | Metairie side |
—
|
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: Metairie side | Statement: [Lake Pontchartrain Causeway, tollCollectionLocation, Metairie side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tollCollectionLocation Context triple: [Lake Pontchartrain Causeway, tollCollectionLocation, Metairie side]
-
A.
tollFacilityName
Indicates the name assigned to a toll facility where tolls are collected.
-
B.
tollRoadOf
Indicates that a road segment is a toll road belonging to or associated with a particular roadway, route, or transportation network.
-
C.
isTollFacilityOf
Indicates that a facility (such as a toll booth, plaza, or gantry) is part of, or used to collect tolls for, a specific toll road or toll transportation infrastructure.
-
D.
tollingAuthority
Indicates the entity that has the authority to impose, collect, or manage a toll on a given route, facility, or service.
-
E.
hasTollBoothsAt
chosen
Indicates that toll booths are present at or associated with a particular location or segment of infrastructure.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:12 p.m.