Triple
T11460626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor Bay Beach |
E271647
|
entity |
| Predicate | nearbyDevelopmentType |
P5744
|
FINISHED |
| Object | villas |
—
|
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: villas | Statement: [Taylor Bay Beach, nearbyDevelopmentType, villas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyDevelopmentType Context triple: [Taylor Bay Beach, nearbyDevelopmentType, villas]
-
A.
hasNearbyDevelopment
Indicates that a development or construction project exists in close physical proximity to the referenced entity.
-
B.
hasNearbyDevelopmentCorridor
Indicates that an entity is located close to, or directly influenced by, a designated development corridor such as a planned or existing zone of concentrated growth or infrastructure.
-
C.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
D.
urbanDevelopmentType
chosen
Indicates the specific category or nature of urban development associated with or applied to an entity (e.g., residential, commercial, mixed-use).
-
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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f384f08190b1150ed1389dd31a |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.