Triple
T23148112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gujarati cinema |
E578248
|
entity |
| Predicate | experiencedResurgenceIn |
P99792
|
FINISHED |
| Object | 2010s |
—
|
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: 2010s | Statement: [Gujarati cinema, experiencedResurgenceIn, 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencedResurgenceIn Context triple: [Gujarati cinema, experiencedResurgenceIn, 2010s]
-
A.
hadResurgenceInCentury
Indicates that something experienced a renewed increase in activity, popularity, or significance during a specified century.
-
B.
hasResurgenceNear
Indicates that an entity experiences a renewed increase, revival, or comeback in close spatial or contextual proximity to another specified entity or location.
-
C.
popularityResurgence
chosen
Indicates a renewed increase in attention, favor, or widespread appeal for something after a period of decline or obscurity.
-
D.
experiencedEpidemic
Indicates that an entity has undergone or been affected by an epidemic event.
-
E.
experiencedFailure
Indicates that an entity has undergone or encountered a failure in performing an action, achieving a goal, or maintaining a desired state.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ecf9e9881908991ede784158f1e |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.