Triple
T15537370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sith Eternal |
E370380
|
entity |
| Predicate | seenInMedium |
P54385
|
FINISHED |
| Object | 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: film | Statement: [Sith Eternal, seenInMedium, film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seenInMedium Context triple: [Sith Eternal, seenInMedium, film]
-
A.
occursInMedium
chosen
Indicates that an event, process, or interaction takes place within or is hosted by a particular medium or environment.
-
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.
mediatisedBy
Indicates that an entity’s communication or interaction is conveyed, shaped, or influenced through a particular medium or media channel rather than occurring directly.
-
D.
introducedInMedium
Indicates that an entity first appears or is initially presented within a specified medium (such as a book, film, game, or other format).
-
E.
featuredMedium
Indicates that one medium (such as an image, video, or other media item) is highlighted or designated as the primary or representative media for 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442f3c688190a599165e526af2ed |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.