Triple
T19301534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Kaluga Oblast |
E482710
|
entity |
| Predicate | hasChargePosition |
P135187
|
FINISHED |
| Object | crown above silver band |
—
|
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: crown above silver band | Statement: [Coat of arms of Kaluga Oblast, hasChargePosition, crown above silver band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChargePosition Context triple: [Coat of arms of Kaluga Oblast, hasChargePosition, crown above silver band]
-
A.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
B.
hasChargeColor
Indicates that one entity is associated with a particular color used to represent its electric charge or charge state.
-
C.
containsCharge
Indicates that one entity includes, holds, or encompasses a specific charge associated with it.
-
D.
hasChargeNumber
Indicates that an entity is associated with a specific charge identifier or charge reference number.
-
E.
canHoldAdditionalChargeOf
Indicates that one entity has the capacity to store or accommodate an additional specified amount of electric charge beyond its current level.
- F. None of above. chosen
Provenance (4 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc8a2a5c8190bfe95e40d3c93a42 |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:31 p.m.