Triple
T35048950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prairie Box |
E1011279
|
entity |
| Predicate | hasWindowArrangement |
P138347
|
FINISHED |
| Object | grouped windows on facade |
—
|
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: grouped windows on facade | Statement: [Prairie Box, hasWindowArrangement, grouped windows on facade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWindowArrangement Context triple: [Prairie Box, hasWindowArrangement, grouped windows on facade]
-
A.
typicalWindowArrangement
chosen
Indicates the usual or standard spatial configuration in which windows are arranged relative to each other in a given context.
-
B.
hasWindowStyle
Indicates that an entity possesses or is characterized by a particular style or type of window.
-
C.
hasWindowDepicting
Indicates that one entity possesses a window on which the other entity is depicted or represented.
-
D.
hasArrangementFocus
Indicates that something is specifically concerned with, directed toward, or centered on the arrangement or organization of another thing.
-
E.
hasUpdatedArrangement
Indicates that an existing arrangement between entities has been modified or brought to a more recent version.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f785ca8fa4819088713fd7a58fa229 |
completed | May 3, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.