Triple
T1039479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Section 202 Supportive Housing for the Elderly Program |
E22437
|
entity |
| Predicate | relatedProgramType |
P2192
|
FINISHED |
| Object | assisted housing |
—
|
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: assisted housing | Statement: [Section 202 Supportive Housing for the Elderly Program, relatedProgramType, assisted housing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedProgramType Context triple: [Section 202 Supportive Housing for the Elderly Program, relatedProgramType, assisted housing]
-
A.
programType
chosen
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
B.
establishedProgram
Indicates that an entity has created and put into operation a formal program that is now in an active, ongoing state.
-
C.
relatedPoliticalProgram
Indicates that one political program is associated with, connected to, or contextually linked with another political program.
-
D.
belongsToProgram
Indicates that an entity is a member of, or is associated with, a specific program.
-
E.
relatedService
Indicates that one service is connected or associated with another service in a relevant or dependent way.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b97c64a88190bf1119fdd4940bf3 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b729f8488190b2042bd9c625a833 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.