Triple
T6959258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indican Pictures |
E161326
|
entity |
| Predicate | typeOfRelease |
P3286
|
FINISHED |
| Object | theatrical distribution |
—
|
LITERAL 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: theatrical distribution | Statement: [Indican Pictures, typeOfRelease, theatrical distribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRelease Context triple: [Indican Pictures, typeOfRelease, theatrical distribution]
-
A.
releaseType
chosen
Indicates the kind or category of a release event or version associated with an entity.
-
B.
releaseVersion
Indicates the specific version identifier associated with a particular release of something (e.g., software, product, or document).
-
C.
releaseStatus
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
-
D.
publicRelease
Indicates that something is made available to the general public, typically after any private or restricted access period has ended.
-
E.
releaseChannel
Indicates the distribution pathway or medium through which something (such as a product, update, or content) is made available or delivered to its recipients.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6daedbb4c8190b46846fb1265b937 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.