Triple
T11503502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town of Briny Breezes, Florida |
E272720
|
entity |
| Predicate | propertyOwnershipModel |
P7585
|
FINISHED |
| Object | resident-owned cooperative lots |
—
|
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: resident-owned cooperative lots | Statement: [Town of Briny Breezes, Florida, propertyOwnershipModel, resident-owned cooperative lots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyOwnershipModel Context triple: [Town of Briny Breezes, Florida, propertyOwnershipModel, resident-owned cooperative lots]
-
A.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
-
B.
ownsPropertyIn
Indicates that one entity possesses legal ownership rights over property located within a specified place or jurisdiction.
-
C.
propertyTypeOwned
Indicates that one entity owns a specific type or category of property in relation to another entity.
-
D.
ownershipType
chosen
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
E.
ownedPropertyWith
Indicates a relationship where one entity owns a particular property jointly or in association with 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85de55cbc8190be71c2d03dc044f2 |
completed | April 10, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.