Triple
T39155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master of Business Analytics |
E775
|
entity |
| Predicate | entryRequirement |
P1130
|
FINISHED |
| Object | bachelor’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: bachelor’s degree | Statement: [Master of Business Analytics, entryRequirement, bachelor’s degree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryRequirement Context triple: [Master of Business Analytics, entryRequirement, bachelor’s degree]
-
A.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
B.
eligibilityCriteria
chosen
Indicates the conditions or requirements that must be satisfied for an entity to qualify for or be considered eligible for something.
-
C.
requiresPermitFor
Indicates that one entity must obtain formal permission or authorization before performing an action involving another entity.
-
D.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
E.
requiredDesignElement
Indicates that one entity must include, use, or incorporate another entity as a necessary design component or feature.
- 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24b4d5bd08190a3a48eb26e67768c |
completed | Feb. 28, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69a24ab6141881908701106aa97e4735 |
completed | Feb. 28, 2026, 1:53 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.