Triple
T10366169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breathe (2017 film) |
E244255
|
entity |
| Predicate | portraysCondition |
P50333
|
FINISHED |
| Object | polio |
—
|
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: polio | Statement: [Breathe (2017 film), portraysCondition, polio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysCondition Context triple: [Breathe (2017 film), portraysCondition, polio]
-
A.
portraysState
chosen
Indicates that one entity visually or symbolically represents or depicts the condition, status, or situation of another entity.
-
B.
presentCondition
Indicates that an entity currently has or exhibits a particular state, situation, or condition.
-
C.
holdsUnderCondition
Indicates that one fact, rule, or relationship remains valid only when a specified condition or set of conditions is satisfied.
-
D.
portrayalFeature
Indicates that one entity serves as a characteristic, aspect, or attribute highlighted in the depiction or representation of another entity.
-
E.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e96f25f48190a41c8b0206b9238c |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, noon