Triple
T37675887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junior Research Fellowship (JRF) |
E938092
|
entity |
| Predicate | eligibleDegreeLevel |
P149244
|
FINISHED |
| Object | postgraduate |
—
|
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: postgraduate | Statement: [Junior Research Fellowship (JRF), eligibleDegreeLevel, postgraduate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleDegreeLevel Context triple: [Junior Research Fellowship (JRF), eligibleDegreeLevel, postgraduate]
-
A.
eligibleDegree
Indicates that an academic degree qualifies its holder to be considered eligible for a particular program, position, or requirement.
-
B.
possibleDegreeLevel
chosen
Indicates the academic or qualification level that an entity can potentially attain, offer, or be associated with.
-
C.
grantsDegreeLevel
Indicates that an institution or program confers a specific academic degree level (such as bachelor’s, master’s, or doctorate) upon completion.
-
D.
haveDegree
Indicates that an entity possesses or has obtained a specific academic or professional degree.
-
E.
academicDegree
Indicates that an entity holds or has been awarded a specific academic degree.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.