Triple
T25864835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blekinge coat of arms |
E651582
|
entity |
| Predicate | hasMainCharge |
P184834
|
FINISHED |
| Object | oak tree |
—
|
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: oak tree | Statement: [Blekinge coat of arms, hasMainCharge, oak tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCharge Context triple: [Blekinge coat of arms, hasMainCharge, oak tree]
-
A.
mainCharge
Indicates that one charge in a set of legal accusations is designated as the primary or most significant offense.
-
B.
hasCentralCharge
Indicates that an entity is associated with, or characterized by, a specific central charge value in a given theoretical or physical framework.
-
C.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
D.
primaryCharge
Indicates that one charge is designated as the main or most significant charge associated with an entity or case, typically among multiple possible charges.
-
E.
chiefCharge
Indicates that one entity holds the primary responsibility, leadership, or authority over another entity or activity.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: April 22, 2026, 8:06 a.m.