Triple
T24741861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia segment of Capital Beltway |
E618584
|
entity |
| Predicate | expressLanesBrand |
P133890
|
FINISHED |
| Object | 495 Express Lanes |
—
|
NE NERFINISHED |
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: 495 Express Lanes | Statement: [Virginia segment of Capital Beltway, expressLanesBrand, 495 Express Lanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expressLanesBrand Context triple: [Virginia segment of Capital Beltway, expressLanesBrand, 495 Express Lanes]
-
A.
brandLine
Indicates that one brand is a specific product line or sub-brand offered under another brand.
-
B.
commuterBrand
Indicates a relationship where a brand is specifically associated with or targeted toward commuter use or commuting contexts.
-
C.
catalogBrand
Indicates that a brand is associated with, or offered within, a particular catalog.
-
D.
isBrand
chosen
Indicates that one entity functions as the commercial brand or label associated with another entity.
-
E.
fareBrand
Indicates the specific fare category or brand under which a ticket or booking is sold, defining its associated rules, benefits, and restrictions.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:16 a.m.