Triple
T23371889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knickerbocker Village |
E593496
|
entity |
| Predicate | hasRentRegulationStatus |
P100452
|
FINISHED |
| Object | rent-stabilized |
—
|
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: rent-stabilized | Statement: [Knickerbocker Village, hasRentRegulationStatus, rent-stabilized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRentRegulationStatus Context triple: [Knickerbocker Village, hasRentRegulationStatus, rent-stabilized]
-
A.
isRentControlled
chosen
Indicates that a property is subject to legal regulations limiting the amount and/or rate at which its rent can be increased.
-
B.
rentControlledBy
Indicates that the use or occupancy of a property is subject to rent control regulations administered or enforced by a specified authority or entity.
-
C.
hasZoningRestriction
Indicates that an entity is subject to a specific zoning-related limitation or regulatory constraint.
-
D.
leaseArea
Indicates that a specified area of property or land is subject to a lease agreement between parties.
-
E.
hasLeisureTenant
Indicates that an entity has another entity as a tenant specifically for leisure-related use or activities.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3af45ec8190a32aa4e5f04f6756 |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.