Triple
T18171459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Peekskill |
E435033
|
entity |
| Predicate | hasPropertyOwnersAssociation |
P36350
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lake Peekskill, hasPropertyOwnersAssociation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPropertyOwnersAssociation Context triple: [Lake Peekskill, hasPropertyOwnersAssociation, yes]
-
A.
hasCommunityAssociation
Indicates that an entity is linked to, affiliated with, or participates in a specific community or community-based organization.
-
B.
hasNeighborhoodAssociation
chosen
Indicates that an entity is associated with, or falls under the jurisdiction of, a particular neighborhood association.
-
C.
hasAssociatedEstate
Indicates that one entity is linked to, or has responsibility for, a particular estate or property.
-
D.
ownsPropertyIn
Indicates that one entity possesses legal ownership rights over property located within a specified place or jurisdiction.
-
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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df56190c8190a3644333f9050a10 |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.