Triple
T29352940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natural Sciences Tripos |
E744361
|
entity |
| Predicate | admissionRoute |
P111918
|
FINISHED |
| Object | UCAS |
—
|
NE NERFINISHED |
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: UCAS | Statement: [Natural Sciences Tripos, admissionRoute, UCAS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionRoute Context triple: [Natural Sciences Tripos, admissionRoute, UCAS]
-
A.
admissionsPath
chosen
Indicates the route, process, or sequence of steps through which an entity gains admission to an institution, program, or service.
-
B.
primaryAdmissionRoute
Indicates the main pathway or method through which an entity is initially admitted, accepted, or brought into a system or context.
-
C.
admissionSource
Indicates the origin or point of referral from which an entity (typically a person or case) was admitted into a system, institution, or process.
-
D.
administrationRoute
Indicates the method or pathway by which a substance or treatment is delivered to a subject or system.
-
E.
admissionPolicy
Indicates the rules or criteria governing whether and how entities are allowed to be admitted or granted access.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6695d19d48190b710de76e8666504 |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:08 p.m.