Triple
T13964615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudge |
E335890
|
entity |
| Predicate | admissionFactor |
P43396
|
FINISHED |
| Object | sporting ability |
—
|
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: sporting ability | Statement: [Rudge, admissionFactor, sporting ability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionFactor Context triple: [Rudge, admissionFactor, sporting ability]
-
A.
admissionType
Indicates the category or manner in which an entity (such as a person or case) is formally accepted or admitted into a system, institution, or process.
-
B.
admissionResult
Indicates the outcome or decision of an admission process for an applicant or entity.
-
C.
admissionsBasedOn
chosen
Indicates that acceptance or entry decisions are determined according to specified criteria, factors, or conditions.
-
D.
controlsAdmissionsFor
Indicates that one entity has authority or responsibility over managing and deciding admissions for another entity.
-
E.
hasAdmission
Indicates that an entity possesses or is associated with a specific admission event, record, or status (such as being admitted to a place, program, or institution).
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e7e24f08190ba939a8044860033 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.