Triple
T25446207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kollywood |
E637643
|
entity |
| Predicate | distributionRegionsInclude |
P158838
|
FINISHED |
| Object | Sri Lanka |
—
|
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: Sri Lanka | Statement: [Kollywood, distributionRegionsInclude, Sri Lanka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributionRegionsInclude Context triple: [Kollywood, distributionRegionsInclude, Sri Lanka]
-
A.
distributionRegionsInclude
chosen
Indicates that certain geographic or market regions are encompassed within the overall distribution coverage of a product or service.
-
B.
includedRegions
Indicates that certain regions are contained within, or form part of, a larger specified region or set of regions.
-
C.
eligibleRegion
Indicates the geographic area within which something (such as an offer, service, or rule) is valid, applicable, or permitted.
-
D.
includesUSRegions
Indicates that something contains or covers one or more specified regions within the United States.
-
E.
catalogRegion
Indicates the geographic or organizational region associated with a given catalog or catalog entry.
- 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_69f5f70346cc8190b7ed6b5a86a508cd |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 2:02 p.m.