Triple
T16960308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luce newsreels |
E411409
|
entity |
| Predicate | screenedBefore |
P125391
|
FINISHED |
| Object | feature films |
—
|
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: feature films | Statement: [Luce newsreels, screenedBefore, feature films]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenedBefore Context triple: [Luce newsreels, screenedBefore, feature films]
-
A.
hasScreened
Indicates that one entity has shown, displayed, or evaluated another entity, typically in the context of presenting media or conducting a review or check.
-
B.
screenedWith
Indicates that one entity is examined, tested, or evaluated using another entity as the screening method, tool, or criterion.
-
C.
screenedAtSection
Indicates that something (such as a film, video, or media item) is shown or presented in a specific section or subdivision of a larger event or venue.
-
D.
firstScreenedAs
Indicates that an entity was initially shown, presented, or tested in a particular screening context or medium.
-
E.
hasSecurityScreening
Indicates that an entity is subject to, or has undergone, a security screening process.
- F. None of above. chosen
Provenance (4 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01f9ba881908dc8820b92869a63 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:31 a.m.