Triple
T23655625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of the Canton of Jura |
E584290
|
entity |
| Predicate | sideWithCrosier |
P145367
|
FINISHED |
| Object | hoist side |
—
|
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: hoist side | Statement: [Flag of the Canton of Jura, sideWithCrosier, hoist side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideWithCrosier Context triple: [Flag of the Canton of Jura, sideWithCrosier, hoist side]
-
A.
orientationOfCrosier
chosen
Indicates the spatial direction or positioning in which a crosier is oriented relative to a reference frame or object.
-
B.
numberOfNotchesOnCrosier
Indicates the relationship that specifies how many notches are present on a given crosier.
-
C.
traditionalSideOfCross
Indicates the side of a cross that is considered the customary or historically recognized orientation in a given tradition.
-
D.
singleSideOf
Indicates that one entity constitutes a single side or face of another entity, typically within a larger multi-sided structure or object.
-
E.
onSide
Indicates that one entity is positioned along or adjacent to the side of another entity.
- 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.