Triple
T34373687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smoking/No Smoking |
E882228
|
entity |
| Predicate | hasSeparableScreenings |
P201018
|
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: [Smoking/No Smoking, hasSeparableScreenings, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeparableScreenings Context triple: [Smoking/No Smoking, hasSeparableScreenings, yes]
-
A.
hasScreening
Indicates that one entity conducts, hosts, or is associated with a particular screening event involving another entity.
-
B.
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.
-
C.
screenedBefore
Indicates that one entity was screened or shown at an earlier time than another entity.
-
D.
screenedWith
Indicates that one entity is examined, tested, or evaluated using another entity as the screening method, tool, or criterion.
-
E.
screeningPattern
Indicates a recurring or structured way in which screenings (such as tests, evaluations, or showings) are scheduled, organized, or carried out between entities.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
| PDg | Predicate description generation | batch_69ffc15434c8819093aa3b33813613be |
completed | May 9, 2026, 11:20 p.m. |
Created at: May 1, 2026, 1:59 a.m.