Triple
T2740595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patrick Henry College |
E60739
|
entity |
| Predicate | admissionsProfile |
P738
|
FINISHED |
| Object | highly selective |
—
|
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: highly selective | Statement: [Patrick Henry College, admissionsProfile, highly selective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionsProfile Context triple: [Patrick Henry College, admissionsProfile, highly selective]
-
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.
admissionsLevel
Indicates the degree or category of access, entry, or acceptance granted in an admissions context.
-
C.
academicProfile
Indicates the relationship that captures an entity’s academic background, qualifications, and scholarly activities or achievements.
-
D.
officialAdmissionBy
Indicates that an entity is formally accepted, enrolled, or granted entry by an authorized official or institution.
-
E.
typicalAdmissionSelectivity
chosen
Indicates the usual level of competitiveness or restrictiveness in admitting applicants to an institution or program.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb2f210881909126307cc92ebfef |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.