Triple
T19143073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NO-DO |
E468605
|
entity |
| Predicate | mandatoryScreening |
P9177
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [NO-DO, mandatoryScreening, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mandatoryScreening Context triple: [NO-DO, mandatoryScreening, yes]
-
A.
commonlyScreenedOn
Indicates that something (such as a film, show, or content) is regularly or typically shown or broadcast on a particular platform, channel, or venue.
-
B.
inspectionRequired
Indicates that an entity must undergo an inspection before it can proceed, be used, or be approved.
-
C.
screenedWith
Indicates that one entity is examined, tested, or evaluated using another entity as the screening method, tool, or criterion.
-
D.
screeningType
chosen
Indicates the specific method or category of screening applied in a screening process or evaluation.
-
E.
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.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e976e340819098efccc30b2eef0e |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.