Triple
T29332862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabash Ramudu |
E743824
|
entity |
| Predicate | workLocationOfProductionCompany |
P131522
|
FINISHED |
| Object | Chennai |
—
|
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: Chennai | Statement: [Sabash Ramudu, workLocationOfProductionCompany, Chennai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workLocationOfProductionCompany Context triple: [Sabash Ramudu, workLocationOfProductionCompany, Chennai]
-
A.
productionCompanyLocation
chosen
Indicates the relationship between a production company and the geographic location where it is based or operates.
-
B.
productionCompanyCountry
Indicates the country in which a production company involved in creating a work is based or registered.
-
C.
placeOfOriginOfWork
Indicates the location where a work (such as an artwork, literary piece, or other creation) was originally produced or created.
-
D.
ownedProductionCompany
Indicates that one entity previously possessed ownership or controlling interest in a production company.
-
E.
productionCompanyOfWork
Indicates that a company is responsible for producing a particular creative work (such as a film, TV show, or similar production).
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 1:30 p.m.