Triple
T25454518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mollywood |
E637876
|
entity |
| Predicate | hasDistributionMarket |
P8091
|
FINISHED |
| Object | Kerala |
—
|
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: Kerala | Statement: [Mollywood, hasDistributionMarket, Kerala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistributionMarket Context triple: [Mollywood, hasDistributionMarket, Kerala]
-
A.
hasDistributionType
Indicates the type or pattern of distribution associated with an entity, specifying how something is spread, allocated, or made available.
-
B.
hasDistributions
Indicates that an entity is associated with one or more distributions through which it is delivered, provided, or made available.
-
C.
hasDistributionForm
Indicates that an entity is associated with a particular physical or pharmaceutical form in which it is distributed or made available.
-
D.
distributesIn
chosen
Indicates that one entity allocates or hands out something (e.g., items, resources, information) within or across a specified area, group, or context.
-
E.
isDistributedThrough
Indicates that something is supplied, circulated, or made available to others via a particular channel, medium, or distribution mechanism.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 21, 2026, 2:04 p.m.