Triple
T16811277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Choice Summer Movie |
E408616
|
entity |
| Predicate | typicalVoterAgeRange |
P53772
|
FINISHED |
| Object | 13–19 |
—
|
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: 13–19 | Statement: [Choice Summer Movie, typicalVoterAgeRange, 13–19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVoterAgeRange Context triple: [Choice Summer Movie, typicalVoterAgeRange, 13–19]
-
A.
typicalAgeOfVoters
chosen
Indicates the usual or most common age range of individuals who participate as voters in elections or voting processes.
-
B.
votingAge
Indicates the minimum age at which an individual is legally permitted to vote.
-
C.
typicalVoters
Indicates that the subject entity is a representative or characteristic member of the group of voters associated with the object entity.
-
D.
eligibleVoters
Indicates that the referenced entities are legally permitted and qualified to vote in a given election or jurisdiction.
-
E.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
- 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.