Triple
T23655593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of the Canton of Jura |
E584289
|
entity |
| Predicate | isFlagBasisFor |
P2421
|
FINISHED |
| Object | Flag of the Canton of Jura |
—
|
NE NERFINISHED |
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: Flag of the Canton of Jura | Statement: [Coat of arms of the Canton of Jura, isFlagBasisFor, Flag of the Canton of Jura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFlagBasisFor Context triple: [Coat of arms of the Canton of Jura, isFlagBasisFor, Flag of the Canton of Jura]
-
A.
hasBasisIn
Indicates that one entity is founded, derived, or justified on the grounds of another entity.
-
B.
isStateFlagOf
Indicates that one entity is the official state flag representing the specified state or region.
-
C.
isOnFlagOf
Indicates that something (typically a symbol, image, or design element) appears on or is depicted on a flag.
-
D.
isBaseFor
chosen
Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
-
E.
isFundamental
Indicates that something is a basic, essential, or foundational element upon which other things depend or are built.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b35b19e48190866a19ed8b7086d0 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.