Triple
T29559000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muthal Mariyathai |
E749983
|
entity |
| Predicate | leadStudioSystem |
P167450
|
FINISHED |
| Object | Tamil film industry |
E39755
|
NE 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: Tamil film industry | Statement: [Muthal Mariyathai, leadStudioSystem, Tamil film industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadStudioSystem Context triple: [Muthal Mariyathai, leadStudioSystem, Tamil film industry]
-
A.
leadStudioStar
Indicates that a person is the primary or top-billed star in a studio’s production.
-
B.
leadStudioHead
Indicates that one entity serves as the primary or head studio leader responsible for another entity (such as a project, production, or organization).
-
C.
madeInStudioSystem
Indicates that a work was produced under a formal studio system, typically involving centralized control over production, distribution, and creative decisions.
-
D.
studioManager
Indicates that one entity holds managerial responsibility or oversight for a studio associated with another entity.
-
E.
liveOrStudio
Indicates whether something (typically a performance or recording) was done live or in a studio setting.
- F. None of above. chosen
Provenance (5 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d1c12688190a93492438e18b74e |
completed | May 2, 2026, 9:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27abfb0dbc8190acf49b1bfd25eb66 |
completed | June 9, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 5:18 p.m.