Triple
T11486109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland Route 24 |
E272281
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Bel Air area |
E393889
|
NE 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: Bel Air area | Statement: [Maryland Route 24, serves, Bel Air area]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bel Air area Context triple: [Maryland Route 24, serves, Bel Air area]
-
A.
Bel Air
Bel Air is an affluent residential neighborhood on Los Angeles’s Westside, known for its large estates, exclusivity, and celebrity residents.
-
B.
Bel Air
Bel Air is a small historic town in Harford County, Maryland, serving as the county seat and regional center for government, commerce, and culture.
-
C.
Bel Air
Bel Air is a historic plantation estate in the United States, notable for its preserved architecture and ties to the region’s antebellum agricultural history.
-
D.
Bel Air, Maryland
chosen
Bel Air, Maryland is a small town in Harford County that serves as a residential and commercial hub in northeastern Maryland.
-
E.
Bradwell Area
Bradwell Area is a Church of England episcopal area within the Diocese of Chelmsford, overseen by the Area Bishop of Bradwell.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85a1fc9688190aacc2eed64229b79 |
completed | April 10, 2026, 2:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e60451a89081909f9534fee6cb809f |
completed | April 20, 2026, 10:47 a.m. |
Created at: April 8, 2026, 9:36 p.m.