Triple
T22453777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBTA bus route 93 |
E555058
|
entity |
| Predicate | hasStopArea |
P9950
|
FINISHED |
| Object | North End |
—
|
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: North End | Statement: [MBTA bus route 93, hasStopArea, North End]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: North End Context triple: [MBTA bus route 93, hasStopArea, North End]
-
A.
North End
chosen
North End is a historic waterfront neighborhood in Boston known for its Italian-American culture, narrow streets, and notable Revolutionary-era sites.
-
B.
North End
North End is a small village in Essex, England, known primarily as a rural residential area within the Chelmsford district.
-
C.
North End
North End is a residential and commercial district on Portsea Island in Portsmouth, England, known for its traditional high street and dense urban housing.
-
D.
North End
North End is a residential neighborhood in Bridgeport, Connecticut, known for its suburban character, parks, and proximity to Sacred Heart University.
-
E.
North End
North End is the commonly used nickname for the English football club Plymouth Argyle.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4d6368819082cafbbd83339fbf |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 16, 2026, 8:48 p.m.