Triple
T19055999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breezy Point, Queens |
E466396
|
entity |
| Predicate | landOwnershipStructure |
P34249
|
FINISHED |
| Object | cooperative |
—
|
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: cooperative | Statement: [Breezy Point, Queens, landOwnershipStructure, cooperative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landOwnershipStructure Context triple: [Breezy Point, Queens, landOwnershipStructure, cooperative]
-
A.
landTenure
chosen
Indicates the type, conditions, or rights under which land is held, used, or owned by an entity.
-
B.
landholdings
Indicates the extent or collection of land owned, controlled, or held by an entity.
-
C.
landManagement
Indicates how land is planned, used, and controlled over time, including decisions about its conservation, development, and resource use.
-
D.
landholderIn
Indicates that one entity holds legal or recognized ownership or tenancy rights over land located within the jurisdiction or bounds of another entity.
-
E.
ownsLandFor
Indicates that one entity possesses or holds ownership rights to land for the benefit, use, or purpose of 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc056b708190a2b84cbddf0fc2d9 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.