Triple
T920994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blogger |
E19881
|
entity |
| Predicate | monetizationOption |
P16212
|
FINISHED |
| Object | advertising via AdSense |
—
|
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: advertising via AdSense | Statement: [Blogger, monetizationOption, advertising via AdSense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monetizationOption Context triple: [Blogger, monetizationOption, advertising via AdSense]
-
A.
supportsMonetizationProgram
chosen
Indicates that an entity enables or is compatible with a specific monetization program, allowing revenue-generating activities to occur.
-
B.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
-
C.
offersFeature
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
D.
offersEdition
Indicates that one entity provides or makes available a particular version or edition of another entity.
-
E.
offersViewOf
Indicates that one entity provides a vantage point from which another entity can be seen or visually appreciated.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b2944ff88190a260be5355132ba5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.