Triple
T34724108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adonai |
E1001005
|
entity |
| Predicate | significantlyBoosted |
P104827
|
FINISHED |
| Object | Sarkodie international recognition |
—
|
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: Sarkodie international recognition | Statement: [Adonai, significantlyBoosted, Sarkodie international recognition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantlyBoosted Context triple: [Adonai, significantlyBoosted, Sarkodie international recognition]
-
A.
helpedBoostProminenceOf
chosen
Indicates that one entity contributed to increasing the visibility, recognition, or prominence of another entity.
-
B.
typicalBoost
Indicates a standard or commonly expected increase in magnitude, intensity, or effectiveness associated with something.
-
C.
significantlyIntensifiedAfter
Indicates that one condition, effect, or quality became much stronger or more pronounced following another event or state.
-
D.
enhancedBy
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result of another entity.
-
E.
usedWithBoosters
Indicates that something is employed or operated in conjunction with boosters to enhance its effect or performance.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 3:59 p.m.