Triple
T33547595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coat of arms of Thuringia |
E859246
|
entity |
| Predicate | secondaryCharges |
P198320
|
FINISHED |
| Object | stars |
—
|
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: stars | Statement: [coat of arms of Thuringia, secondaryCharges, stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryCharges Context triple: [coat of arms of Thuringia, secondaryCharges, stars]
-
A.
secondaryCharge
Indicates that an entity has an additional, non-primary charge or accusation associated with it, typically accompanying a main or primary charge.
-
B.
centralCharge
Indicates that an entity has a specific central charge value, typically quantifying a key parameter in a conformal or related physical or mathematical theory.
-
C.
mainCharge
Indicates that one charge in a set of legal accusations is designated as the primary or most significant offense.
-
D.
crestAdditionalCharge
Indicates an extra fee or surcharge applied in addition to a base cost, typically associated with a specific crest-related service or item.
-
E.
subsequentFees
Indicates that additional fees are charged or become applicable after an initial fee or primary transaction has occurred.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
| PDg | Predicate description generation | batch_69fedd5915588190bd884054e4be0414 |
completed | May 9, 2026, 7:08 a.m. |
Created at: May 1, 2026, 1:39 a.m.