Triple
T25255711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kannada cinema |
E633167
|
entity |
| Predicate | majorDistributionArea |
P42913
|
FINISHED |
| Object | Karnataka |
—
|
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: Karnataka | Statement: [Kannada cinema, majorDistributionArea, Karnataka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorDistributionArea Context triple: [Kannada cinema, majorDistributionArea, Karnataka]
-
A.
majorDistrict
Indicates that one administrative district is the primary or most significant district associated with another entity or area.
-
B.
macroArea
Indicates a broad geographic or regional grouping within which an entity (such as a language or location) is situated.
-
C.
suburbanAreasDominatedBy
Indicates that one suburban area is predominantly controlled, influenced, or characterized by another entity (such as a group, activity, or demographic).
-
D.
shareMajorCityRegion
Indicates that two entities are associated with the same major city or its surrounding metropolitan region.
-
E.
distributorTerritory
chosen
Indicates the geographic area or market in which a distributor is authorized or responsible to sell or distribute products or services.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 21, 2026, 1:13 p.m.