Triple
T99878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBA |
E2016
|
entity |
| Predicate | commonOutcome |
P3100
|
FINISHED |
| Object | salary increase |
—
|
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: salary increase | Statement: [MBA, commonOutcome, salary increase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonOutcome Context triple: [MBA, commonOutcome, salary increase]
-
A.
oftenAccompaniedBy
chosen
Indicates that one entity is frequently found together with, occurs alongside, or is commonly associated in presence or use with another entity.
-
B.
legalOutcome
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
C.
notableOutcome
Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
-
D.
historicalOutcome
Indicates the result or consequence that an event, action, or situation produced in a historical context.
-
E.
hasConsequence
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a253b95d4c81909d1f2bc37e799c44 |
completed | Feb. 28, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69a24ebfc5a88190bdd1653b9fa541fe |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.