Triple
T22381422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bing |
E553282
|
entity |
| Predicate | forcedConsumption |
P4672
|
FINISHED |
| Object | must watch advertisements |
—
|
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: must watch advertisements | Statement: [Bing, forcedConsumption, must watch advertisements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedConsumption Context triple: [Bing, forcedConsumption, must watch advertisements]
-
A.
consumes
Indicates that one entity eats, drinks, or otherwise uses up another entity as a resource or nourishment.
-
B.
forcedBy
chosen
Indicates that an entity is compelled or coerced into an action or state by another entity.
-
C.
consumptionState
Indicates the current status or condition of how something is being used up, consumed, or depleted.
-
D.
isConsumedIn
Indicates that one entity is used up, ingested, or otherwise expended as part of a process, event, or action involving another entity.
-
E.
forcedActionDescribedIn
Indicates that an action was carried out under compulsion or coercion as described in a particular source or description.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582c05fc8190836ae008426177a5 |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.