Triple
T25782140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Entrance Examination |
E649317
|
entity |
| Predicate | admissionsStage |
P159817
|
FINISHED |
| Object | pre-GCSE entry |
—
|
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: pre-GCSE entry | Statement: [Common Entrance Examination, admissionsStage, pre-GCSE entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionsStage Context triple: [Common Entrance Examination, admissionsStage, pre-GCSE entry]
-
A.
admissionsSystem
Indicates a relationship where an entity functions as or is associated with a system that manages or processes admissions decisions or applications.
-
B.
admissionCycle
Indicates the specific application or enrollment period during which an admission-related event or decision takes place.
-
C.
admissionsLevel
Indicates the degree or category of access, entry, or acceptance granted in an admissions context.
-
D.
admissionsStandard
Indicates that there is a specified criterion or set of requirements that must be met for admission to a program, institution, or opportunity.
-
E.
admissionsPath
Indicates the route, process, or sequence of steps through which an entity gains admission to an institution, program, or service.
- 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_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 22, 2026, 5:51 a.m.