Triple
T22381412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bing |
E553282
|
entity |
| Predicate | rebelsBy |
P147439
|
FINISHED |
| Object | delivering on-air rant |
—
|
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: delivering on-air rant | Statement: [Bing, rebelsBy, delivering on-air rant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebelsBy Context triple: [Bing, rebelsBy, delivering on-air rant]
-
A.
rebelsAgainst
Indicates that one entity actively resists, opposes, or rises up against the authority, control, or established order represented by another entity.
-
B.
typeOfRebel
Indicates that one entity is a rebel belonging to, or classified under, a particular type or category of rebellion.
-
C.
associatedRebellion
Indicates a relationship where an entity is linked to, involved in, or connected with a particular rebellion or uprising.
-
D.
commandedByRebels
Indicates that the authority or control over an entity is exercised by rebel forces or insurgent groups.
-
E.
rebelBase
Indicates a location that serves as a primary stronghold, headquarters, or operational center for a rebel or resistance group.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e7342e9a0081909257210a81c96b29 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:45 p.m.