Triple
T29245230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiyaan Vikram |
E741422
|
entity |
| Predicate | breakthroughFilm |
P115242
|
FINISHED |
| Object | Sethu |
—
|
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: Sethu | Statement: [Chiyaan Vikram, breakthroughFilm, Sethu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breakthroughFilm Context triple: [Chiyaan Vikram, breakthroughFilm, Sethu]
-
A.
breakthrough
Indicates a significant and often sudden advance or discovery that overcomes a major obstacle in a process, field, or endeavor.
-
B.
breakthroughBy
Indicates that a significant discovery, innovation, or advance was achieved or brought about by a particular agent or entity.
-
C.
gaveBreakthroughTo
Indicates that one entity provided another entity with a decisive insight, discovery, or advancement that significantly improved their progress or understanding.
-
D.
markedBreakthroughOf
Indicates that an event, action, or development signified a major breakthrough or turning point for something.
-
E.
breakthroughWorkOf
chosen
Indicates that one work is recognized as the major breakthrough or career-defining achievement of a particular creator or 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66488889c819098b7354fc2f72f90 |
completed | May 2, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 12:32 p.m.