Triple
T2545965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boring Bricks |
E57901
|
entity |
| Predicate | proposedUseCase |
P19962
|
FINISHED |
| Object | low-income 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: low-income housing | Statement: [Boring Bricks, proposedUseCase, low-income housing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedUseCase Context triple: [Boring Bricks, proposedUseCase, low-income housing]
-
A.
plannedUseOf
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
B.
hasUseCase
chosen
Indicates that one entity is employed, applied, or utilized as a solution or method to address a particular need, problem, or scenario associated with another entity.
-
C.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
D.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
E.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2c285288190b41fc0188879623a |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.