Triple
T27392884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodhaven, Michigan |
E691586
|
entity |
| Predicate | isResidentialCorridorPart |
P85888
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Woodhaven, Michigan, isResidentialCorridorPart, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResidentialCorridorPart Context triple: [Woodhaven, Michigan, isResidentialCorridorPart, true]
-
A.
isResidentialRegionPart
Indicates that one residential region is a constituent or included part of another, larger residential region.
-
B.
isInResidentialArea
Indicates that something is located within a residential area, such as a neighborhood or zone primarily designated for housing.
-
C.
isResidentialBuildingIn
Indicates that a residential building is located within or belongs to a specified geographic area or administrative region.
-
D.
isPartOfCorridorSystem
chosen
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
E.
isResidentialUnitOf
Indicates that a specific residential unit (e.g., apartment, house) belongs to or is part of a larger property, building, or complex.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cae21408190836baa6f4a1b52a2 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:26 p.m.