Triple
T7578657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OUAC |
E179425
|
entity |
| Predicate | handlesApplicationsForLevel |
P77965
|
FINISHED |
| Object | undergraduate |
—
|
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: undergraduate | Statement: [OUAC, handlesApplicationsForLevel, undergraduate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesApplicationsForLevel Context triple: [OUAC, handlesApplicationsForLevel, undergraduate]
-
A.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
B.
recognizesLevel
Indicates that one entity acknowledges, identifies, or is aware of the degree, rank, or intensity associated with another entity.
-
C.
coversLevel
Indicates that one entity includes or encompasses a particular level or layer of another entity or system.
-
D.
appliesIf
Indicates that a rule, condition, or operation is applicable only when certain specified criteria or circumstances are met.
-
E.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f97460a481909d61fba555567b66 |
completed | March 27, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:51 p.m.