Triple
T19346447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ammos Beach |
E483890
|
entity |
| Predicate | nearAmenity |
P61362
|
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: [Ammos Beach, nearAmenity, restaurants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearAmenity Context triple: [Ammos Beach, nearAmenity, restaurants]
-
A.
nearbyTo
chosen
Indicates that one entity is located close in distance or position to another entity.
-
B.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
-
C.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
D.
proximityToLandmark
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
-
E.
nearbyUrbanCenter
Indicates that one location is geographically close to an urban center, such as a city or large town.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185b7d348190ba195056bb32c765 |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.