Triple
T37668242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coal Black and de Sebben Dwarfs |
E937878
|
entity |
| Predicate | screeningRestrictions |
P72055
|
FINISHED |
| Object | rarely shown publicly |
—
|
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: rarely shown publicly | Statement: [Coal Black and de Sebben Dwarfs, screeningRestrictions, rarely shown publicly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screeningRestrictions Context triple: [Coal Black and de Sebben Dwarfs, screeningRestrictions, rarely shown publicly]
-
A.
hasScreening
Indicates that one entity conducts, hosts, or is associated with a particular screening event involving another entity.
-
B.
eligibilityRestrictedBy
Indicates that an entity’s eligibility for something is limited, constrained, or conditioned by another specified factor or rule.
-
C.
spectatorRestrictions
chosen
Indicates limitations, conditions, or rules governing who may be present as spectators and under what circumstances.
-
D.
screenedWith
Indicates that one entity is examined, tested, or evaluated using another entity as the screening method, tool, or criterion.
-
E.
viewingLimit
Indicates a restriction on how many times or for how long something can be viewed.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:18 p.m.