Triple
T21075382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SE Division Street |
E519218
|
entity |
| Predicate | hasAmenityTypeAlong |
P124384
|
FINISHED |
| Object | restaurants |
—
|
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: restaurants | Statement: [SE Division Street, hasAmenityTypeAlong, restaurants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAmenityTypeAlong Context triple: [SE Division Street, hasAmenityTypeAlong, restaurants]
-
A.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
-
B.
hasRegionalAmenity
Indicates that a region provides or contains a specific amenity or facility within its area.
-
C.
hasFacilityType
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
D.
hasCivicAmenity
Indicates that an entity possesses, provides, or is associated with a public facility or service intended for community use.
-
E.
typicalAmenity
chosen
Indicates that something is a common or characteristic amenity typically associated with a given entity or context.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702d690dc8190839968b562e6b8bb |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:48 p.m.