Triple
T1329340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Air Force checkerboard |
E28604
|
entity |
| Predicate | graphicType |
P21655
|
FINISHED |
| Object | geometric design |
—
|
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: geometric design | Statement: [Polish Air Force checkerboard, graphicType, geometric design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphicType Context triple: [Polish Air Force checkerboard, graphicType, geometric design]
-
A.
graphics
Indicates a relationship where one entity is responsible for creating, providing, or handling visual representations or graphical content for another entity or context.
-
B.
formationType
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
-
C.
depictionType
Indicates the specific manner or style in which something is visually represented or depicted.
-
D.
artworkType
Indicates the specific category or kind of artwork that characterizes the relationship between the subject and the artwork.
-
E.
representationType
chosen
Indicates the specific form or mode in which something is represented or expressed (e.g., as a symbol, image, model, or description).
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c30c948190afc6342b3dcda948 |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.