Triple
T35074345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Four Square |
E1011969
|
entity |
| Predicate | hasTypicalPorchType |
P199733
|
FINISHED |
| Object | one-story front porch |
—
|
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: one-story front porch | Statement: [American Four Square, hasTypicalPorchType, one-story front porch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalPorchType Context triple: [American Four Square, hasTypicalPorchType, one-story front porch]
-
A.
hasPorch
Indicates that one entity (typically a building or residence) includes or is equipped with a porch as part of its structure.
-
B.
hasPorchLocation
Indicates the spatial location or placement of a porch relative to another referenced entity.
-
C.
hasPorchSupport
Indicates that a structure or building includes a supporting element specifically for a porch.
-
D.
hasPorchUse
Indicates that something includes or permits the use of a porch as part of its function, design, or occupancy.
-
E.
hasPorchLength
Indicates that one entity (typically a building or structure) has a porch whose length is specified or measured by the related value or entity.
- F. None of above. chosen
Provenance (4 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69ff528536d481909caefe52fcd8aaa7 |
completed | May 9, 2026, 3:28 p.m. |
Created at: May 3, 2026, 4:01 p.m.