Triple
T26318217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mint |
E662029
|
entity |
| Predicate | monetizedBy |
P16212
|
FINISHED |
| Object | financial product referrals |
—
|
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: financial product referrals | Statement: [Mint, monetizedBy, financial product referrals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monetizedBy Context triple: [Mint, monetizedBy, financial product referrals]
-
A.
hasMonetizationFocus
Indicates that one entity is oriented toward or primarily concerned with generating revenue or financial returns from another entity or activity.
-
B.
monetaryComponent
Indicates that something is a financial element or part of a larger monetary value, structure, or transaction.
-
C.
supportsMonetizationProgram
chosen
Indicates that an entity enables or is compatible with a specific monetization program, allowing revenue-generating activities to occur.
-
D.
hasMonetaryComponent
Indicates that something includes, involves, or is associated with a monetary or financial element.
-
E.
monetaryValue
Indicates the amount of money associated with an entity, event, or transaction.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f28e9588190b76581e150f4f27d |
completed | May 2, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 10:26 p.m.