Triple
T13343069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silent film |
E317871
|
entity |
| Predicate | wasSupplantedBy |
P101
|
FINISHED |
| Object | synchronized sound 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: synchronized sound film | Statement: [Silent film, wasSupplantedBy, synchronized sound film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSupplantedBy Context triple: [Silent film, wasSupplantedBy, synchronized sound film]
-
A.
wasSupersededBy
chosen
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
B.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
C.
introducedAsSuccessorOf
Indicates that one entity was formally presented or designated to take over the role, position, or function previously held by another entity.
-
D.
statusAfterSupersession
Indicates the status or condition an entity holds after it has been superseded by another entity.
-
E.
wasAbolishedBy
Indicates that an institution, practice, law, or entity ceased to exist or operate as a result of an action taken by another entity.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e8839b48190b164414b418e756c |
completed | April 11, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:31 p.m.