Triple
T16811261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Choice Summer Movie |
E408616
|
entity |
| Predicate | votingOpenTo |
P1084
|
FINISHED |
| Object | teenage audiences |
—
|
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: teenage audiences | Statement: [Choice Summer Movie, votingOpenTo, teenage audiences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingOpenTo Context triple: [Choice Summer Movie, votingOpenTo, teenage audiences]
-
A.
votingIs
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
-
B.
votingStatus
Indicates whether an entity is currently eligible, registered, or has participated in a voting process.
-
C.
canVoteOn
chosen
Indicates that an entity has the right or permission to participate in a decision-making process by casting a vote on a specific item, issue, or proposal.
-
D.
votingScope
Indicates the range or domain within which a voting action or decision is valid, applicable, or authorized.
-
E.
votingTiming
Indicates the temporal relationship specifying when a voting action occurs relative to a defined event or period.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2d0793c81909d938ac174a6e63a |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.