Triple
T24484800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law and Business Program |
E617475
|
entity |
| Predicate | offeredAtLevel |
P156482
|
FINISHED |
| Object | graduate |
—
|
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: graduate | Statement: [Law and Business Program, offeredAtLevel, graduate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredAtLevel Context triple: [Law and Business Program, offeredAtLevel, graduate]
-
A.
mayOfferLevel
Indicates that an entity is permitted or authorized to provide or deliver a specified level or tier of something (such as service, access, or qualification).
-
B.
offeredIn
Indicates that something is made available or provided within a particular context, setting, or medium.
-
C.
meetsAtLevel
Indicates that two or more entities encounter or interact with each other at a specific hierarchical, structural, or progression level.
-
D.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
-
E.
mayBeOfferedFor
Indicates that one entity can potentially be provided or made available as an option to another entity.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a9d795288190916368e3cec1f666 |
completed | April 30, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:21 a.m.