Triple
T4539928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Council of Lombardy |
E107501
|
entity |
| Predicate | usesSealImage |
P57576
|
FINISHED |
| Object | emblem of the Lombardy Region |
—
|
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: emblem of the Lombardy Region | Statement: [Regional Council of Lombardy, usesSealImage, emblem of the Lombardy Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSealImage Context triple: [Regional Council of Lombardy, usesSealImage, emblem of the Lombardy Region]
-
A.
usedSeal
Indicates that an entity has applied or employed a seal (e.g., for closure, authentication, or protection) on another entity.
-
B.
sealType
Indicates the specific kind or category of seal associated with an entity or connection.
-
C.
secondSealAssociatedWith
Indicates an associative relationship in which something is linked or connected specifically to a second seal.
-
D.
signatureImage
Indicates that an entity has an associated image that visually represents its signature.
-
E.
inscriptionUsedWith
Indicates that a particular inscription is employed together with, or in association with, another object, tool, or context in which it is applied or interpreted.
- 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_69bd43f922788190b7edfa294e39b178 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57bb5c0c819092ebb2dd3310f5f8 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:04 p.m.