Triple
T37956831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raakh |
E946888
|
entity |
| Predicate | cultFollowingIn |
P189665
|
FINISHED |
| Object | Hindi cinema |
—
|
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: Hindi cinema | Statement: [Raakh, cultFollowingIn, Hindi cinema]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultFollowingIn Context triple: [Raakh, cultFollowingIn, Hindi cinema]
-
A.
followsDisc
Indicates that one entity comes after another in a sequence or order, typically in a discrete or stepwise progression.
-
B.
eraFollowed
Indicates that one historical era comes directly after another in chronological sequence.
-
C.
calledToFollowBy
Indicates that one entity has been summoned, invited, or designated by another entity to follow, accompany, or pursue a path or role associated with that other entity.
-
D.
followerOf
Indicates that one entity subscribes to, tracks, or regularly receives updates from another entity, typically in a social or informational context.
-
E.
followedIn
Indicates that one entity began following or subscribing to another entity, typically in a social or sequential context.
- F. None of above. chosen
Provenance (4 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc7b6c2c88190ad4f58980834053c |
completed | May 6, 2026, 10:59 p.m. |
Created at: May 3, 2026, 4:20 p.m.