Triple
T22049462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andy Flower |
E544844
|
entity |
| Predicate | protestEvent |
P108648
|
FINISHED |
| Object | black armband protest at 2003 Cricket World Cup |
—
|
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: black armband protest at 2003 Cricket World Cup | Statement: [Andy Flower, protestEvent, black armband protest at 2003 Cricket World Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protestEvent Context triple: [Andy Flower, protestEvent, black armband protest at 2003 Cricket World Cup]
-
A.
protests
Indicates that an entity publicly expresses opposition or disapproval toward another entity, action, or situation.
-
B.
notableProtest
Indicates that an entity is recognized for having led, organized, or been centrally involved in a significant protest or demonstration.
-
C.
organizedProtest
chosen
Indicates that an entity planned, coordinated, and carried out a protest event involving participants expressing opposition or support regarding an issue.
-
D.
locationOfNotableProtest
Indicates the place where a significant or notable protest event occurred.
-
E.
protestForm
Indicates the specific method or mode by which a protest or demonstration is carried out.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128323fb08190b9592fd08a96cba0 |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:26 p.m.