Triple
T7827352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scudetto shield |
E181279
|
entity |
| Predicate | typeOfEmblem |
P79228
|
FINISHED |
| Object | champions badge |
—
|
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: champions badge | Statement: [Scudetto shield, typeOfEmblem, champions badge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEmblem Context triple: [Scudetto shield, typeOfEmblem, champions badge]
-
A.
emblemName
Indicates that a specified name is the official or recognized title of an emblem.
-
B.
protectiveEmblemName
Indicates that a given name is the designated title or label of a protective emblem associated with an entity or context.
-
C.
definesEmblem
Indicates that one entity specifies or establishes the official emblem associated with another entity.
-
D.
emblemUsedBy
Indicates that a particular emblem is adopted or employed by a specific entity as its symbol or identifying mark.
-
E.
emblemFeatures
Indicates that an emblem includes or displays specific visual elements or characteristics.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb04a7f3b8819080f8a8283d6118fb |
completed | March 30, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:43 p.m.