Triple
T27860123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kop Stand |
E704202
|
entity |
| Predicate | typicalDesign |
P95346
|
FINISHED |
| Object | single-tiered terrace |
—
|
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: single-tiered terrace | Statement: [Kop Stand, typicalDesign, single-tiered terrace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDesign Context triple: [Kop Stand, typicalDesign, single-tiered terrace]
-
A.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) for another entity.
-
B.
typicalDesignElement
chosen
Indicates that something is a common or characteristic design feature typically found in or associated with another entity.
-
C.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
D.
designTrend
Indicates a prevailing or emerging stylistic direction or pattern that influences how something is designed over a period of time.
-
E.
typicalFabric
Indicates that something is made from or associated with a fabric material that is standard or characteristic for its type.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a002962f6e081909906d6436bae6407 |
completed | May 10, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_6a00284c9c7c8190a77f18a41eee55df |
completed | May 10, 2026, 6:40 a.m. |
Created at: April 27, 2026, 6:17 p.m.