Triple
T18478562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Studies Program |
E451497
|
entity |
| Predicate | typicalDegreeType |
P48121
|
FINISHED |
| Object | master’s degree |
—
|
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: master’s degree | Statement: [Regional Studies Program, typicalDegreeType, master’s degree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDegreeType Context triple: [Regional Studies Program, typicalDegreeType, master’s degree]
-
A.
typicalDegree
Indicates the usual or characteristic level, intensity, or extent to which something holds or applies in a given context.
-
B.
typicalDegreeName
chosen
Indicates the standard or commonly used academic degree title associated with an educational program or qualification.
-
C.
typicalDegreeLevels
Indicates the usual or commonly expected academic degree levels associated with a given entity or context.
-
D.
degreeSystem
Indicates a relationship where an entity’s degree or qualification is defined, classified, or governed by a particular educational or grading system.
-
E.
eligibleDegree
Indicates that an academic degree qualifies its holder to be considered eligible for a particular program, position, or requirement.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53065e8388190bb216dae89f8cf75 |
completed | April 19, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.