Triple
T37210452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mooz-lum |
E922285
|
entity |
| Predicate | hasOriginalNetworkOrPlatform |
P111224
|
FINISHED |
| Object | limited theatrical release |
—
|
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: limited theatrical release | Statement: [Mooz-lum, hasOriginalNetworkOrPlatform, limited theatrical release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalNetworkOrPlatform Context triple: [Mooz-lum, hasOriginalNetworkOrPlatform, limited theatrical release]
-
A.
hasNetworkOfOrigin
Indicates that an entity originates from, or is primarily associated with, a particular network or source network.
-
B.
hasOriginalNetworkFocus
Indicates that an entity’s primary or initial broadcasting or distribution was carried out by a specified network.
-
C.
originalNetworkOrFormat
chosen
Indicates the network, platform, or format in which a work was first originally released or presented.
-
D.
hasOriginalProducer
Indicates that an entity was initially created, manufactured, or produced by a specific producer or organization.
-
E.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
- 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: May 3, 2026, 4:15 p.m.