Triple
T7414162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macaulay Honors College |
E171086
|
entity |
| Predicate | admissionsBasis |
P43396
|
FINISHED |
| Object | merit-based selection |
—
|
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: merit-based selection | Statement: [Macaulay Honors College, admissionsBasis, merit-based selection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionsBasis Context triple: [Macaulay Honors College, admissionsBasis, merit-based selection]
-
A.
admissionsBasedOn
chosen
Indicates that acceptance or entry decisions are determined according to specified criteria, factors, or conditions.
-
B.
admissionsSystem
Indicates a relationship where an entity functions as or is associated with a system that manages or processes admissions decisions or applications.
-
C.
admissionsLevel
Indicates the degree or category of access, entry, or acceptance granted in an admissions context.
-
D.
controlsAdmissionsFor
Indicates that one entity has authority or responsibility over managing and deciding admissions for another entity.
-
E.
recruitmentBasis
Indicates the criteria, grounds, or conditions on which an entity is recruited or selected for a role or position.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c509ac8190876f207267a33a3b |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.