Triple
T25607483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Viz competition |
E641951
|
entity |
| Predicate | prizesInclude |
P111313
|
FINISHED |
| Object | recognition as Iron Viz champion |
—
|
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: recognition as Iron Viz champion | Statement: [Iron Viz competition, prizesInclude, recognition as Iron Viz champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prizesInclude Context triple: [Iron Viz competition, prizesInclude, recognition as Iron Viz champion]
-
A.
isPrizedFor
Indicates that something is highly valued or esteemed because of a particular quality, feature, or benefit it provides.
-
B.
hasAdditionalPrizes
Indicates that an entity offers or is associated with extra prizes beyond the primary or standard ones.
-
C.
prizesAreInternational
Indicates that the prizes associated with an event or activity are available or valid across multiple countries or on a global scale.
-
D.
isNamedPrizeOf
Indicates that one entity is the official name of a prize or award associated with another entity.
-
E.
hasCompetitionPrize
chosen
Indicates that an entity awards or is associated with a specific prize given in the context of a competition.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 4:39 p.m.