Triple
T2687980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarendon Boulevard |
E57529
|
entity |
| Predicate | hasAmenityAlong |
P5622
|
FINISHED |
| Object | bars |
—
|
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: bars | Statement: [Clarendon Boulevard, hasAmenityAlong, bars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAmenityAlong Context triple: [Clarendon Boulevard, hasAmenityAlong, bars]
-
A.
amenity
chosen
Indicates that one entity provides a useful facility, service, or feature that enhances the convenience or comfort of another entity.
-
B.
hasNeighborhoodAlong
Indicates that one entity has a neighboring area or region that extends along the boundary or length of another entity.
-
C.
hasPublicSpaceAlong
Indicates that a public space (such as a park, plaza, or walkway) is located adjacent to or runs alongside the referenced feature or element.
-
D.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
E.
amenityLevel
Indicates the degree or quality of facilities, services, or conveniences provided in relation to something.
- 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9f1ba3081909a349a2f30f8f9c9 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.