Triple
T31808432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celebration Residential Owners Association |
E811937
|
entity |
| Predicate | typeOfAmenityScope |
P157271
|
FINISHED |
| Object | master-planned community amenities |
—
|
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: master-planned community amenities | Statement: [Celebration Residential Owners Association, typeOfAmenityScope, master-planned community amenities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAmenityScope Context triple: [Celebration Residential Owners Association, typeOfAmenityScope, master-planned community amenities]
-
A.
amenityScope
chosen
Indicates the range or extent of services, facilities, or conveniences that an amenity provides or applies to.
-
B.
amenityLevel
Indicates the degree or quality of facilities, services, or conveniences provided in relation to something.
-
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.
amenitiesInclude
Indicates that a place or facility provides or contains specific amenities as part of its features.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00119d821c8190874786391b27ef23 |
completed | May 10, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a001143fb6881909ac0ae8bfea04351 |
completed | May 10, 2026, 5:01 a.m. |
Created at: April 30, 2026, 11:43 p.m.