Triple
T28101700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Normal Love |
E710253
|
entity |
| Predicate | screeningPractice |
P142889
|
FINISHED |
| Object | shown in underground film venues |
—
|
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: shown in underground film venues | Statement: [Normal Love, screeningPractice, shown in underground film venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screeningPractice Context triple: [Normal Love, screeningPractice, shown in underground film venues]
-
A.
screeningType
Indicates the specific method or category of screening applied in a screening process or evaluation.
-
B.
screenedWith
Indicates that one entity is examined, tested, or evaluated using another entity as the screening method, tool, or criterion.
-
C.
screeningBasis
Indicates the underlying reason, criterion, or grounds on which a screening or evaluation is conducted between entities.
-
D.
screeningOutcome
Indicates the result or decision produced by a screening or evaluation process applied to an entity.
-
E.
screeningPattern
chosen
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.
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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6409275e081909c3f102b56d1f132 |
completed | May 2, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:05 p.m.