Triple
T25782134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Entrance Examination |
E649317
|
entity |
| Predicate | examSessionFrequency |
P159257
|
FINISHED |
| Object | multiple times per year |
—
|
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: multiple times per year | Statement: [Common Entrance Examination, examSessionFrequency, multiple times per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examSessionFrequency Context triple: [Common Entrance Examination, examSessionFrequency, multiple times per year]
-
A.
examPeriod
Indicates a time span during which examinations are scheduled to take place.
-
B.
examTime
Indicates the scheduled time at which an exam is to take place.
-
C.
examSystem
Indicates a relationship where an entity functions as or belongs to an examination system, such as a framework or platform for creating, administering, or managing exams.
-
D.
examProvider
Indicates that one entity is the organization or individual responsible for creating, administering, or supplying an exam to another entity.
-
E.
examType
Indicates the specific category or format of an exam associated with an assessment or testing event.
- F. None of above. chosen
Provenance (4 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_69f5fe6175048190afd845628c74830e |
completed | May 2, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 5:51 a.m.