Triple
T23845559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India 2020 |
E591108
|
entity |
| Predicate | highlightsChallenge |
P3362
|
FINISHED |
| Object | poverty eradication |
—
|
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: poverty eradication | Statement: [India 2020, highlightsChallenge, poverty eradication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highlightsChallenge Context triple: [India 2020, highlightsChallenge, poverty eradication]
-
A.
featuredChallengeCup
Indicates that a particular Challenge Cup is highlighted or given special prominence relative to others.
-
B.
hasDanceChallenge
Indicates that one entity presents, initiates, or is associated with a dance challenge involving another entity.
-
C.
highlights
chosen
Indicates that one entity draws special attention to, emphasizes, or visually marks another entity as important or noteworthy.
-
D.
challengeType
Indicates the specific category or kind of challenge associated with an action or relationship between entities.
-
E.
challengeFormat
Indicates that one entity specifies or defines the structure, rules, or format in which a challenge or contest is presented or conducted for another entity.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c88b59688190922d6bf329f08721 |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:09 p.m.