Triple
T37264274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creole cottages |
E924339
|
entity |
| Predicate | typicalPorchFeature |
P199733
|
FINISHED |
| Object | full-width 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: full-width front porch | Statement: [Creole cottages, typicalPorchFeature, full-width front porch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPorchFeature Context triple: [Creole cottages, typicalPorchFeature, full-width front porch]
-
A.
hasTypicalPorchType
chosen
Indicates the usual or characteristic type of porch associated with an entity (such as a building or house).
-
B.
hasPorch
Indicates that one entity (typically a building or residence) includes or is equipped with a porch as part of its structure.
-
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.
hasPorchLocation
Indicates the spatial location or placement of a porch relative to another referenced entity.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.