Triple
T29668317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edenwald |
E750594
|
entity |
| Predicate | hasPublicHousingComplex |
P12192
|
FINISHED |
| Object | Edenwald Houses |
—
|
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: Edenwald Houses | Statement: [Edenwald, hasPublicHousingComplex, Edenwald Houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicHousingComplex Context triple: [Edenwald, hasPublicHousingComplex, Edenwald Houses]
-
A.
hasPublicHousing
chosen
Indicates that a location or jurisdiction provides or contains government-funded residential housing available to the public.
-
B.
hasPublicHousingAuthority
Indicates that an entity is associated with, governed by, or served by a specific public housing authority.
-
C.
isPublicHousing
Indicates that the entity is designated as government-provided or subsidized residential housing intended for public use.
-
D.
hasPublicHouse
Indicates that one entity possesses, operates, or is associated with a public house (such as a bar or pub) as part of its facilities or holdings.
-
E.
hasHousingAccess
Indicates that an entity has the ability, right, or opportunity to obtain or use suitable housing.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 7:02 p.m.