Triple
T27982087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One-Year MBA |
E706650
|
entity |
| Predicate | mayRequireBackground |
P80595
|
FINISHED |
| Object | work experience |
—
|
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: work experience | Statement: [One-Year MBA, mayRequireBackground, work experience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayRequireBackground Context triple: [One-Year MBA, mayRequireBackground, work experience]
-
A.
mayRequireBackgroundIn
chosen
Indicates that performing or understanding one entity may necessitate prior knowledge, experience, or qualifications in another domain or subject.
-
B.
mayRequest
Indicates that one entity is permitted or authorized to make a request to another entity or for a particular resource or action.
-
C.
hasBackground
Indicates that an entity possesses or is associated with a particular background, such as context, setting, or prior circumstances.
-
D.
mayRequireAdditionalStep
Indicates that performing one action, process, or condition can necessitate an extra step beyond the standard or initial sequence.
-
E.
mayIncludeRequirement
Indicates that something can optionally contain or encompass a particular requirement as part of its definition or structure.
- 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_69f63b6a5fec81908e73597e2413bb1e |
completed | May 2, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:45 p.m.