Triple
T30826323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chesapeake Ranch Estates |
E785076
|
entity |
| Predicate | hasPrivateAmenity |
P79291
|
FINISHED |
| Object | private beaches |
—
|
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: private beaches | Statement: [Chesapeake Ranch Estates, hasPrivateAmenity, private beaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrivateAmenity Context triple: [Chesapeake Ranch Estates, hasPrivateAmenity, private beaches]
-
A.
hasCustomerAmenity
Indicates that an entity provides or includes a specific amenity or convenience feature for its customers.
-
B.
amenitiesInclude
chosen
Indicates that a place or facility provides or contains specific amenities as part of its features.
-
C.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
-
D.
typicalAmenity
Indicates that something is a common or characteristic amenity typically associated with a given entity or context.
-
E.
hasRegionalAmenity
Indicates that a region provides or contains a specific amenity or facility within its area.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
Created at: April 29, 2026, 8:44 p.m.