Triple
T6909920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | šahovnica |
E159904
|
entity |
| Predicate | positionOnCoatOfArmsOfCroatia |
P34701
|
FINISHED |
| Object | central shield |
—
|
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: central shield | Statement: [šahovnica, positionOnCoatOfArmsOfCroatia, central shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnCoatOfArmsOfCroatia Context triple: [šahovnica, positionOnCoatOfArmsOfCroatia, central shield]
-
A.
coatOfArmsPosition
Indicates the spatial placement or arrangement of a coat of arms relative to another object, surface, or reference frame.
-
B.
topLeftCantonSymbol
Indicates that the specified symbol appears in the top-left canton (corner section) of a flag or similar rectangular field.
-
C.
bottomRightCantonSymbol
Indicates that a symbol is located in the bottom-right canton (quarter) of a divided field or flag.
-
D.
cantonPosition
Indicates the relative placement or arrangement of a canton within a larger geographic or administrative context.
-
E.
positionOfEmblem
chosen
Indicates the spatial placement or location of an emblem relative to a reference object or surface.
- 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9c00e948190b103a2b2a2738bb1 |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.