Triple
T36347849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Rooster Award |
E895112
|
entity |
| Predicate | combinedFestivalWith |
P128363
|
FINISHED |
| Object | Hundred Flowers Awards |
—
|
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: Hundred Flowers Awards | Statement: [Golden Rooster Award, combinedFestivalWith, Hundred Flowers Awards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinedFestivalWith Context triple: [Golden Rooster Award, combinedFestivalWith, Hundred Flowers Awards]
-
A.
linkedFestival
Indicates that two entities are associated through a common festival, event, or celebration.
-
B.
festivalOrganiser
Indicates that one entity is responsible for planning, coordinating, or managing a festival for another entity or context.
-
C.
associatedFestivalOrCustom
Indicates a festival or custom that is traditionally linked or related to the given entity.
-
D.
linksFestivalTo
Indicates that one entity is associated with, connected to, or participates in a particular festival.
-
E.
relatedFestivalType
chosen
Indicates that one festival is associated with another through a shared or corresponding festival type or category.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.