Triple
T34939662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | šahovnica |
E1007679
|
entity |
| Predicate | positionInCoatOfArms |
P34701
|
FINISHED |
| Object | central element |
—
|
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 element | Statement: [šahovnica, positionInCoatOfArms, central element]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInCoatOfArms Context triple: [šahovnica, positionInCoatOfArms, central element]
-
A.
coatOfArmsPosition
Indicates the spatial placement or arrangement of a coat of arms relative to another object, surface, or reference frame.
-
B.
mountOnCoatOfArms
Indicates that one element is depicted as a heraldic charge or figure placed upon a coat of arms.
-
C.
positionOfEmblem
chosen
Indicates the spatial placement or location of an emblem relative to a reference object or surface.
-
D.
positionInRegalia
Indicates the specific role or rank an individual holds within a formal regalia or ceremonial order.
-
E.
iconographicPosition
Indicates the relative placement or arrangement of elements within an image or visual composition, specifying where something appears in the iconographic layout.
- 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4 p.m.