Triple
T28323346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwibbogen arches |
E717336
|
entity |
| Predicate | typicalLocationOfDisplay |
P155223
|
FINISHED |
| Object | window |
—
|
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: window | Statement: [Schwibbogen arches, typicalLocationOfDisplay, window]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocationOfDisplay Context triple: [Schwibbogen arches, typicalLocationOfDisplay, window]
-
A.
currentDisplayLocation
Indicates the location or context where something is presently being shown or rendered.
-
B.
typicalLocationOnProduct
chosen
Indicates the usual physical place or area on a product where something (e.g., a feature, label, or component) is commonly found.
-
C.
displayedAt
Indicates that one entity is presented or exhibited at a particular location, venue, or event.
-
D.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
E.
typicalUseLocation
Indicates the usual or most common location where an entity is used or operates.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a008ac37dc081908d360574912f40ec |
completed | May 10, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_6a008a67d73881909855ab4cfca3c399 |
completed | May 10, 2026, 1:38 p.m. |
Created at: April 28, 2026, 12:26 a.m.