Triple
T30441353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monroe Houses |
E774451
|
entity |
| Predicate | publicHousingAgency |
P40850
|
FINISHED |
| Object | New York City Housing Authority |
—
|
NE NERFINISHED |
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: New York City Housing Authority | Statement: [Monroe Houses, publicHousingAgency, New York City Housing Authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicHousingAgency Context triple: [Monroe Houses, publicHousingAgency, New York City Housing Authority]
-
A.
hasPublicHousingAuthority
chosen
Indicates that an entity is associated with, governed by, or served by a specific public housing authority.
-
B.
isPublicHousing
Indicates that the entity is designated as government-provided or subsidized residential housing intended for public use.
-
C.
notPublicHousingEstate
Indicates that a given housing-related entity is explicitly classified as not being a public housing estate.
-
D.
providedHousingFor
Indicates that one entity supplied or arranged housing or accommodation for another entity.
-
E.
hasPublicHousing
Indicates that a location or jurisdiction provides or contains government-funded residential housing available to the public.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: April 29, 2026, 8:08 p.m.