Triple
T25782105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Entrance Examination |
E649317
|
entity |
| Predicate | typicalCandidateAge |
P57433
|
FINISHED |
| Object | 13 |
—
|
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 | Statement: [Common Entrance Examination, typicalCandidateAge, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCandidateAge Context triple: [Common Entrance Examination, typicalCandidateAge, 13]
-
A.
typicalAgeOfVoters
Indicates the usual or most common age range of individuals who participate as voters in elections or voting processes.
-
B.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
-
C.
typicalCandidate
Indicates that an entity is a standard or representative example of what is usually considered a candidate in a given context.
-
D.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
E.
typicalAgeAtSelection
chosen
Indicates the usual or most common age at which an entity is chosen or selected for a particular role, status, or process.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: April 22, 2026, 5:51 a.m.