Triple
T27982100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One-Year MBA |
E706650
|
entity |
| Predicate | hasWorkloadIntensity |
P16069
|
FINISHED |
| Object | higher than traditional MBA |
—
|
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: higher than traditional MBA | Statement: [One-Year MBA, hasWorkloadIntensity, higher than traditional MBA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkloadIntensity Context triple: [One-Year MBA, hasWorkloadIntensity, higher than traditional MBA]
-
A.
hasSignificantWorkType
Indicates that an entity is associated with a primary or notably important type or category of work.
-
B.
hasRideIntensity
Indicates the degree or level of intensity associated with a ride experience.
-
C.
isIntense
chosen
Indicates that something exhibits a high degree of strength, force, or concentration in its quality, effect, or activity.
-
D.
isVigorous
Indicates that an entity exhibits strong energy, intensity, or forcefulness in its actions or behavior.
-
E.
hasWorkOn
Indicates that one entity is associated with, contributes to, or performs work on another entity (such as a project, task, or artifact).
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 27, 2026, 7:45 p.m.