Triple
T30692204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goddess of the Silent Screen |
E781358
|
entity |
| Predicate | appliedToMedium |
P149528
|
FINISHED |
| Object | silent film |
—
|
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 film | Statement: [Goddess of the Silent Screen, appliedToMedium, silent film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToMedium Context triple: [Goddess of the Silent Screen, appliedToMedium, silent film]
-
A.
applicableMedium
chosen
Indicates that a particular medium or material is suitable for use with, or can be effectively applied by, the referenced entity.
-
B.
basedOnMedium
Indicates that one entity is derived from, adapted from, or created using another entity as its source medium or foundational material.
-
C.
occursInMedium
Indicates that an event, process, or interaction takes place within or is hosted by a particular medium or environment.
-
D.
usedMedium
Indicates that an action or communication was carried out through a particular medium or channel.
-
E.
affectedMedium
Indicates that a medium (such as a material, environment, or channel) is impacted or influenced by a specified action, process, or event.
- 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_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: April 29, 2026, 8:33 p.m.