Triple
T30692219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goddess of the Silent Screen |
E781358
|
entity |
| Predicate | impliesMedium |
P166
|
FINISHED |
| Object | silent cinema |
—
|
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: silent cinema | Statement: [Goddess of the Silent Screen, impliesMedium, silent cinema]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesMedium Context triple: [Goddess of the Silent Screen, impliesMedium, silent cinema]
-
A.
implies
Indicates that the truth of one statement guarantees or leads logically to the truth of another statement.
-
B.
subsequentMedium
Indicates that one medium or format follows another in a sequence, typically as a later or alternative form of the same content or communication.
-
C.
medium
chosen
Indicates that an entity serves as the means, channel, or intermediary through which an action, communication, or effect is carried out between other entities.
-
D.
plannedMedium
Indicates that a particular medium or channel has been designated in advance for use in carrying out an action or communication.
-
E.
requiresMedium
Indicates that an action or process depends on or must be carried out within a specific medium or environment to occur or be valid.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:33 p.m.