Triple
T3703041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wailea Beach |
E80824
|
entity |
| Predicate | hasNearbyAmenities |
P5648
|
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: [Wailea Beach, hasNearbyAmenities, restaurants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyAmenities Context triple: [Wailea Beach, hasNearbyAmenities, restaurants]
-
A.
hasNearbyFacility
chosen
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
B.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
C.
hasAttractionNearby
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
-
D.
meetsNear
Indicates that two entities meet or come together at a location that is in close proximity to a specified reference point or area.
-
E.
amenity
Indicates that one entity provides a useful facility, service, or feature that enhances the convenience or comfort of another entity.
- 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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc54925b48190b23d2a14ef825abc |
completed | March 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69adb84eeca48190bb4de637e9f0e27a |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:33 p.m.